[
https://issues.apache.org/jira/browse/MAPREDUCE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797943#action_12797943
]
Hadoop QA commented on MAPREDUCE-1359:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12429718/MAPREDUCE-1359.1.patch
against trunk revision 897076.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/365/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/365/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/365/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h6.grid.sp2.yahoo.net/365/console
This message is automatically generated.
> TypedBytes TestIO doesn't mkdir its test dir first
> --------------------------------------------------
>
> Key: MAPREDUCE-1359
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1359
> Project: Hadoop Map/Reduce
> Issue Type: Test
> Components: contrib/streaming
> Affects Versions: 0.21.0, 0.22.0
> Reporter: Todd Lipcon
> Assignee: Anatoli Fomenko
> Attachments: MAPREDUCE-1359.1.patch
>
>
> TestIO fails when run alone since it doesn't mkdir its test directory in the
> setUp function. This JIRA should fix it and update the tests to use junit 4
> style.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
