hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nigel Daley <nda...@yahoo-inc.com>
Subject Re: [jira] Commented: (HADOOP-1020) Path class on Windows seems broken
Date Wed, 28 Feb 2007 01:43:24 GMT
Argh!  These -1 are false negatives.  I changed the way I determine  
the max acceptable warnings, by doing a quick build of trunk (ant  
tar) and compare this to the number of warnings from patched build  
and test (ant test tar).  The problem is that the test target causes  
compile-core-test to be executed twice, and thus the total number of  
warnings are different.  A fix is now in place for this and I'll test  
it out tonight.


On Feb 27, 2007, at 4:19 PM, Hadoop QA (JIRA) wrote:

>
>     [ https://issues.apache.org/jira/browse/HADOOP-1020? 
> page=com.atlassian.jira.plugin.system.issuetabpanels:comment- 
> tabpanel#action_12476462 ]
>
> Hadoop QA commented on HADOOP-1020:
> -----------------------------------
>
> -1, because javac generated 768 warnings (more than the acceptable  
> 766 warnings) when testing the latest attachment (http:// 
> issues.apache.org/jira/secure/attachment/12352189/ 
> HADOOP-1020-2.patch) against trunk revision http://svn.apache.org/ 
> repos/asf/lucene/hadoop/trunk/512461. Please note that this message  
> is automatically generated and may represent a problem with the  
> automation system and not the patch. Results are at http:// 
> lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch
>
>> Path class on Windows seems broken
>> ----------------------------------
>>
>>                 Key: HADOOP-1020
>>                 URL: https://issues.apache.org/jira/browse/ 
>> HADOOP-1020
>>             Project: Hadoop
>>          Issue Type: Bug
>>          Components: dfs
>>    Affects Versions: 0.11.1
>>            Reporter: Nigel Daley
>>         Assigned To: Doug Cutting
>>             Fix For: 0.12.0
>>
>>         Attachments: HADOOP-1020-2.patch, HADOOP-1020.patch,  
>> TestPath.java.patch
>>
>>
>> Executing this code:
>> Path file = new Path("file:///", "C:/trunk/build/test/data");    
>> or   Path file = new Path("C:/trunk/build/test/data");
>> FileSystem fs = file.getFileSystem(conf);
>> fs.mkdirs(file))
>> produces this exception.  It looks like it's defaulting to the  
>> DistributedFileSystem.
>> 2007-02-14 11:36:31,700 INFO  mapred.TaskInProgress  
>> (TaskInProgress.java:updateStatus(296)) - Error from  
>> task_0001_m_000000_0: java.lang.IllegalArgumentException:  
>> Pathname /C:/trunk/build/test/data from C:/trunk/build/test/data  
>> is not a valid DFS filename.
>>         at org.apache.hadoop.dfs.DistributedFileSystem.getPath 
>> (DistributedFileSystem.java:111)
>>         at org.apache.hadoop.dfs.DistributedFileSystem.mkdirs 
>> (DistributedFileSystem.java:211)
>>         at org.apache.hadoop.mapred.MRCaching$MapClass.configure 
>> (MRCaching.java:68)
>>         at org.apache.hadoop.util.ReflectionUtils.setConf 
>> (ReflectionUtils.java:50)
>>         at org.apache.hadoop.util.ReflectionUtils.newInstance 
>> (ReflectionUtils.java:70)
>>         at org.apache.hadoop.mapred.MapRunner.configure 
>> (MapRunner.java:34)
>>         at org.apache.hadoop.util.ReflectionUtils.setConf 
>> (ReflectionUtils.java:50)
>>         at org.apache.hadoop.util.ReflectionUtils.newInstance 
>> (ReflectionUtils.java:70)
>>         at org.apache.hadoop.mapred.MapTask.run(MapTask.java:178)
>>         at org.apache.hadoop.mapred.TaskTracker$Child.main 
>> (TaskTracker.java:1396)
>
> -- 
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>


Mime
View raw message