[
https://issues.apache.org/jira/browse/HDFS-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789685#action_12789685
]
Hadoop QA commented on HDFS-825:
--------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12427682/HDFS-825.patch
against trunk revision 889494.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+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 passed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/143/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/143/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/143/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/143/console
This message is automatically generated.
> Build fails to pull latest hadoop-core-* artifacts
> --------------------------------------------------
>
> Key: HDFS-825
> URL: https://issues.apache.org/jira/browse/HDFS-825
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: build
> Affects Versions: 0.21.0, 0.22.0
> Reporter: Konstantin Boudnik
> Assignee: Konstantin Boudnik
> Priority: Critical
> Attachments: HDFS-825.patch, latest-mod-check.patch
>
>
> I've noticed on more than one occasion that Ivy cache has staled Common
> SNAPSHOT jar files. In some cases I've seen more than a month old files. In
> fact, some very bad problems weren't tested at all, because changes in Common
> weren't pulled into, say, HDFS where the tests had to be executed.
> I've noticed the same problem with MapReduce just today: latest cached
> snapshot of Common was a week old.
> One can run clean ivy cache to make sure that latest versions are pulled
> down. However, it's inconvenient and undesirable to do every time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
