Return-Path: Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: (qmail 66456 invoked from network); 12 Dec 2009 05:04:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Dec 2009 05:04:43 -0000 Received: (qmail 83297 invoked by uid 500); 12 Dec 2009 05:04:43 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 83140 invoked by uid 500); 12 Dec 2009 05:04:41 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 83108 invoked by uid 99); 12 Dec 2009 05:04:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Dec 2009 05:04:40 +0000 X-ASF-Spam-Status: No, hits=-10.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Dec 2009 05:04:38 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 75ECF234C1F2 for ; Fri, 11 Dec 2009 21:04:18 -0800 (PST) Message-ID: <328610264.1260594258481.JavaMail.jira@brutus> Date: Sat, 12 Dec 2009 05:04:18 +0000 (UTC) From: "Hadoop QA (JIRA)" To: hdfs-issues@hadoop.apache.org Subject: [jira] Commented: (HDFS-825) Build fails to pull latest hadoop-core-* artifacts In-Reply-To: <590580013.1260415041551.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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.