You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@hadoop.apache.org by Konstantin Boudnik <co...@apache.org> on 2011/03/05 00:04:33 UTC
Re: Hadoop-Mapreduce-trunk-Commit - Build # 621 - Still Failing
Looks like the same symptoms are affecting Common trunk builds
https://hudson.apache.org/hudson/job/Hadoop-Common-trunk-Commit/516/
Have our build env. has been changed recently?
--
Take care,
Konstantin (Cos) Boudnik
On Thu, Mar 3, 2011 at 21:36, Konstantin Boudnik <co...@apache.org> wrote:
> That seems like settings.xml has been modified, but then it'd affect
> other builds as well. Unless we are using different machines/users for
> different component's builds.
>
> On Thu, Mar 3, 2011 at 13:41, Todd Lipcon <to...@cloudera.com> wrote:
>> Anyone understand why we can't seem to publish to apache maven anymore?
>>
>> -Todd
>>
>> On Thu, Mar 3, 2011 at 1:35 PM, Apache Hudson Server
>> <hu...@hudson.apache.org> wrote:
>>> See https://hudson.apache.org/hudson/job/Hadoop-Mapreduce-trunk-Commit/621/
>>>
>>> ###################################################################################
>>> ########################## LAST 60 LINES OF THE CONSOLE ###########################
>>> [...truncated 4464 lines...]
>>> [javac] Compiling 11 source files to /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/build-fi/system/test/classes
>>> [javac] Note: Some input files use or override a deprecated API.
>>> [javac] Note: Recompile with -Xlint:deprecation for details.
>>>
>>> jar-test-system:
>>>
>>> -do-jar-test:
>>> [jar] Building jar: /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/build-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT.jar
>>> [jar] Building jar: /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/build-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT-sources.jar
>>>
>>> set-version:
>>> [copy] Copying 1 file to /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/ivy
>>> [copy] Copying 1 file to /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/ivy
>>> [copy] Copying 1 file to /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/ivy
>>> [copy] Copying 1 file to /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/ivy
>>>
>>> clean-sign:
>>>
>>> sign:
>>>
>>> signanddeploy:
>>>
>>> simpledeploy:
>>> [artifact:install-provider] Installing provider: org.apache.maven.wagon:wagon-http:jar:1.0-beta-2:runtime
>>> [artifact:deploy] Deploying to https://repository.apache.org/content/repositories/snapshots
>>> [artifact:deploy] [INFO] Retrieving previous build number from apache.snapshots.https
>>> [artifact:deploy] Uploading: org/apache/hadoop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.jar to apache.snapshots.https
>>> [artifact:deploy] Uploaded 1741K
>>> [artifact:deploy] An error has occurred while processing the Maven artifact tasks.
>>> [artifact:deploy] Diagnosis:
>>> [artifact:deploy]
>>> [artifact:deploy] Error deploying artifact 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to transfer file: https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.jar. Return code is: 401
>>>
>>> BUILD FAILED
>>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/build.xml:1528: Error deploying artifact 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to transfer file: https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.jar. Return code is: 401
>>>
>>> Total time: 3 minutes 20 seconds
>>>
>>>
>>> ======================================================================
>>> ======================================================================
>>> STORE: saving artifacts
>>> ======================================================================
>>> ======================================================================
>>>
>>>
>>> mv: cannot stat `build/*.tar.gz': No such file or directory
>>> mv: cannot stat `build/test/findbugs': No such file or directory
>>> mv: cannot stat `build/docs/api': No such file or directory
>>> Build Failed
>>> [FINDBUGS] Skipping publisher since build result is FAILURE
>>> Recording fingerprints
>>> Archiving artifacts
>>> Recording test results
>>> Publishing Javadoc
>>> Publishing Clover coverage report...
>>> No Clover report will be published due to a Build Failure
>>> Email was triggered for: Failure
>>> Sending email for trigger: Failure
>>>
>>>
>>>
>>> ###################################################################################
>>> ############################## FAILED TESTS (if any) ##############################
>>> No tests ran.
>>>
>>
>>
>>
>> --
>> Todd Lipcon
>> Software Engineer, Cloudera
>>
>
Re: Hadoop-Mapreduce-trunk-Commit - Build # 621 - Still Failing
Posted by Todd Lipcon <to...@cloudera.com>.
On Mon, Mar 7, 2011 at 5:06 PM, Greg Roelofs <ro...@yahoo-inc.com> wrote:
> [general@ moved to Bcc; this seems like a pure dev issue now.]
Good call.
>
> If the hypothetical "rm -rf" can be found, perhaps simply changing it to
> nuke only ~/.m2/repository would suffice? Or does settings.xml live below
> that?
Yea... anyone have any ideas which build might be rming it?
>
> Restoring it as one of the first steps of a Hudson build is probably the
> best approach, though (especially if it's restored from svn or somewhere
> with change-history).
The issue with putting it somewhere with change history is that it
needs to be private, since it contains a password. So, if we move it
to a private part of the SVN, then we have a bootstrapping problem of
where to keep the authentication for SVN :)
For now, how about we put it in
/homes/hudson/hadoop-ci-maven-settings.xml or something, not
versioned, and then add a bit to the nightly build script that cps it
into place?
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
Re: Hadoop-Mapreduce-trunk-Commit - Build # 621 - Still Failing
Posted by Greg Roelofs <ro...@yahoo-inc.com>.
[general@ moved to Bcc; this seems like a pure dev issue now.]
Todd Lipcon wrote:
> It looks like something automated must be rming the settings.xml file.
> Maybe one of our builds has an "rm -Rf ~/.m2" in it or something?
(probably "rm -rf")
> Or put it in the spot in ~/.m2 but with permissions set to make it
> harder to remove?
I don't believe there's any combination of owner/perms that would protect
it against "rm -rf" while still allowing the creation of the repository/
dir in there. Possibly the sticky bit or something similar (I think one
of them prevents deletion of another user's files even if the directory
has appropriate write-permissions), but I'm not sure even that would work.
If the hypothetical "rm -rf" can be found, perhaps simply changing it to
nuke only ~/.m2/repository would suffice? Or does settings.xml live below
that?
Restoring it as one of the first steps of a Hudson build is probably the
best approach, though (especially if it's restored from svn or somewhere
with change-history).
Greg
Re: Hadoop-Mapreduce-trunk-Commit - Build # 621 - Still Failing
Posted by Greg Roelofs <ro...@yahoo-inc.com>.
[general@ moved to Bcc; this seems like a pure dev issue now.]
Todd Lipcon wrote:
> It looks like something automated must be rming the settings.xml file.
> Maybe one of our builds has an "rm -Rf ~/.m2" in it or something?
(probably "rm -rf")
> Or put it in the spot in ~/.m2 but with permissions set to make it
> harder to remove?
I don't believe there's any combination of owner/perms that would protect
it against "rm -rf" while still allowing the creation of the repository/
dir in there. Possibly the sticky bit or something similar (I think one
of them prevents deletion of another user's files even if the directory
has appropriate write-permissions), but I'm not sure even that would work.
If the hypothetical "rm -rf" can be found, perhaps simply changing it to
nuke only ~/.m2/repository would suffice? Or does settings.xml live below
that?
Restoring it as one of the first steps of a Hudson build is probably the
best approach, though (especially if it's restored from svn or somewhere
with change-history).
Greg
Re: Hadoop-Mapreduce-trunk-Commit - Build # 621 - Still Failing
Posted by Todd Lipcon <to...@cloudera.com>.
It looks like something automated must be rming the settings.xml file.
Maybe one of our builds has an "rm -Rf ~/.m2" in it or something?
According to the docs I've found, we could also put this setting in
$ANT_HOME/etc. Maybe that's a safer spot?
Or put it in the spot in ~/.m2 but with permissions set to make it
harder to remove?
-Todd
On Fri, Mar 4, 2011 at 4:34 PM, Konstantin Boudnik <co...@apache.org> wrote:
> Thanks a lot Giri!
> I guess this is another reason to have CM in place for the build machines.
>
> On Fri, Mar 4, 2011 at 16:30, Giridharan Kesavan
> <gk...@yahoo-inc.com> wrote:
>> It looks like settings.xml file is deleted by someone while cleaning the m2
>> repository (my guess). I ve copied it back.
>> I'm triggering a build to verify this.
>>
>> -Giri
>>
>>
>> On 3/4/11 4:21 PM, "Giridharan Kesavan" <gk...@yahoo-inc.com> wrote:
>>
>>> I'm lookin into it..
>>> -Giri
>>>
>>> On 3/4/11 3:04 PM, "Konstantin Boudnik" <co...@apache.org> wrote:
>>>
>>>> Looks like the same symptoms are affecting Common trunk builds
>>>> https://hudson.apache.org/hudson/job/Hadoop-Common-trunk-Commit/516/
>>>> Have our build env. has been changed recently?
>>>> --
>>>> Take care,
>>>> Konstantin (Cos) Boudnik
>>>>
>>>> On Thu, Mar 3, 2011 at 21:36, Konstantin Boudnik <co...@apache.org> wrote:
>>>>> That seems like settings.xml has been modified, but then it'd affect
>>>>> other builds as well. Unless we are using different machines/users for
>>>>> different component's builds.
>>>>>
>>>>> On Thu, Mar 3, 2011 at 13:41, Todd Lipcon <to...@cloudera.com> wrote:
>>>>>> Anyone understand why we can't seem to publish to apache maven anymore?
>>>>>>
>>>>>> -Todd
>>>>>>
>>>>>> On Thu, Mar 3, 2011 at 1:35 PM, Apache Hudson Server
>>>>>> <hu...@hudson.apache.org> wrote:
>>>>>>> See
>>>>>>> https://hudson.apache.org/hudson/job/Hadoop-Mapreduce-trunk-Commit/621/
>>>>>>>
>>>>>>>
>> ##########################################################################>>>>>
>> #
>>>>>>> ########
>>>>>>> ########################## LAST 60 LINES OF THE CONSOLE
>>>>>>> ###########################
>>>>>>> [...truncated 4464 lines...]
>>>>>>> [javac] Compiling 11 source files to
>>>>>>>
>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
>> b
>>>>>>> uild-fi/system/test/classes
>>>>>>> [javac] Note: Some input files use or override a deprecated API.
>>>>>>> [javac] Note: Recompile with -Xlint:deprecation for details.
>>>>>>>
>>>>>>> jar-test-system:
>>>>>>>
>>>>>>> -do-jar-test:
>>>>>>> [jar] Building jar:
>>>>>>>
>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
>> b
>>>>>>> uild-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT.jar
>>>>>>> [jar] Building jar:
>>>>>>>
>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
>> b
>>>>>>> uild-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT-sources.jar
>>>>>>>
>>>>>>> set-version:
>>>>>>> [copy] Copying 1 file to
>>>>>>>
>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
>> i
>>>>>>> vy
>>>>>>> [copy] Copying 1 file to
>>>>>>>
>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
>> i
>>>>>>> vy
>>>>>>> [copy] Copying 1 file to
>>>>>>>
>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
>> i
>>>>>>> vy
>>>>>>> [copy] Copying 1 file to
>>>>>>>
>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
>> i
>>>>>>> vy
>>>>>>>
>>>>>>> clean-sign:
>>>>>>>
>>>>>>> sign:
>>>>>>>
>>>>>>> signanddeploy:
>>>>>>>
>>>>>>> simpledeploy:
>>>>>>> [artifact:install-provider] Installing provider:
>>>>>>> org.apache.maven.wagon:wagon-http:jar:1.0-beta-2:runtime
>>>>>>> [artifact:deploy] Deploying to
>>>>>>> https://repository.apache.org/content/repositories/snapshots
>>>>>>> [artifact:deploy] [INFO] Retrieving previous build number from
>>>>>>> apache.snapshots.https
>>>>>>> [artifact:deploy] Uploading:
>>>>>>>
>> org/apache/hadoop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110>>>>>
>> 3
>>>>>>> 03.213523-60.jar to apache.snapshots.https
>>>>>>> [artifact:deploy] Uploaded 1741K
>>>>>>> [artifact:deploy] An error has occurred while processing the Maven
>>>>>>> artifact
>>>>>>> tasks.
>>>>>>> [artifact:deploy] Diagnosis:
>>>>>>> [artifact:deploy]
>>>>>>> [artifact:deploy] Error deploying artifact
>>>>>>> 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to
>>>>>>> transfer file:
>>>>>>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/ha>>>>>
>> d
>>>>>>>
>> oop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.>>>>>
>> j
>>>>>>> ar. Return code is: 401
>>>>>>>
>>>>>>> BUILD FAILED
>>>>>>>
>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
>> b
>>>>>>> uild.xml:1528: Error deploying artifact
>>>>>>> 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to
>>>>>>> transfer file:
>>>>>>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/ha>>>>>
>> d
>>>>>>>
>> oop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.>>>>>
>> j
>>>>>>> ar. Return code is: 401
>>>>>>>
>>>>>>> Total time: 3 minutes 20 seconds
>>>>>>>
>>>>>>>
>>>>>>> ======================================================================
>>>>>>> ======================================================================
>>>>>>> STORE: saving artifacts
>>>>>>> ======================================================================
>>>>>>> ======================================================================
>>>>>>>
>>>>>>>
>>>>>>> mv: cannot stat `build/*.tar.gz': No such file or directory
>>>>>>> mv: cannot stat `build/test/findbugs': No such file or directory
>>>>>>> mv: cannot stat `build/docs/api': No such file or directory
>>>>>>> Build Failed
>>>>>>> [FINDBUGS] Skipping publisher since build result is FAILURE
>>>>>>> Recording fingerprints
>>>>>>> Archiving artifacts
>>>>>>> Recording test results
>>>>>>> Publishing Javadoc
>>>>>>> Publishing Clover coverage report...
>>>>>>> No Clover report will be published due to a Build Failure
>>>>>>> Email was triggered for: Failure
>>>>>>> Sending email for trigger: Failure
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>> ##########################################################################>>>>>
>> #
>>>>>>> ########
>>>>>>> ############################## FAILED TESTS (if any)
>>>>>>> ##############################
>>>>>>> No tests ran.
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Todd Lipcon
>>>>>> Software Engineer, Cloudera
>>>>>>
>>>>>
>>>
>>
>>
>
--
Todd Lipcon
Software Engineer, Cloudera
Re: Hadoop-Mapreduce-trunk-Commit - Build # 621 - Still Failing
Posted by Todd Lipcon <to...@cloudera.com>.
It looks like something automated must be rming the settings.xml file.
Maybe one of our builds has an "rm -Rf ~/.m2" in it or something?
According to the docs I've found, we could also put this setting in
$ANT_HOME/etc. Maybe that's a safer spot?
Or put it in the spot in ~/.m2 but with permissions set to make it
harder to remove?
-Todd
On Fri, Mar 4, 2011 at 4:34 PM, Konstantin Boudnik <co...@apache.org> wrote:
> Thanks a lot Giri!
> I guess this is another reason to have CM in place for the build machines.
>
> On Fri, Mar 4, 2011 at 16:30, Giridharan Kesavan
> <gk...@yahoo-inc.com> wrote:
>> It looks like settings.xml file is deleted by someone while cleaning the m2
>> repository (my guess). I ve copied it back.
>> I'm triggering a build to verify this.
>>
>> -Giri
>>
>>
>> On 3/4/11 4:21 PM, "Giridharan Kesavan" <gk...@yahoo-inc.com> wrote:
>>
>>> I'm lookin into it..
>>> -Giri
>>>
>>> On 3/4/11 3:04 PM, "Konstantin Boudnik" <co...@apache.org> wrote:
>>>
>>>> Looks like the same symptoms are affecting Common trunk builds
>>>> https://hudson.apache.org/hudson/job/Hadoop-Common-trunk-Commit/516/
>>>> Have our build env. has been changed recently?
>>>> --
>>>> Take care,
>>>> Konstantin (Cos) Boudnik
>>>>
>>>> On Thu, Mar 3, 2011 at 21:36, Konstantin Boudnik <co...@apache.org> wrote:
>>>>> That seems like settings.xml has been modified, but then it'd affect
>>>>> other builds as well. Unless we are using different machines/users for
>>>>> different component's builds.
>>>>>
>>>>> On Thu, Mar 3, 2011 at 13:41, Todd Lipcon <to...@cloudera.com> wrote:
>>>>>> Anyone understand why we can't seem to publish to apache maven anymore?
>>>>>>
>>>>>> -Todd
>>>>>>
>>>>>> On Thu, Mar 3, 2011 at 1:35 PM, Apache Hudson Server
>>>>>> <hu...@hudson.apache.org> wrote:
>>>>>>> See
>>>>>>> https://hudson.apache.org/hudson/job/Hadoop-Mapreduce-trunk-Commit/621/
>>>>>>>
>>>>>>>
>> ##########################################################################>>>>>
>> #
>>>>>>> ########
>>>>>>> ########################## LAST 60 LINES OF THE CONSOLE
>>>>>>> ###########################
>>>>>>> [...truncated 4464 lines...]
>>>>>>> [javac] Compiling 11 source files to
>>>>>>>
>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
>> b
>>>>>>> uild-fi/system/test/classes
>>>>>>> [javac] Note: Some input files use or override a deprecated API.
>>>>>>> [javac] Note: Recompile with -Xlint:deprecation for details.
>>>>>>>
>>>>>>> jar-test-system:
>>>>>>>
>>>>>>> -do-jar-test:
>>>>>>> [jar] Building jar:
>>>>>>>
>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
>> b
>>>>>>> uild-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT.jar
>>>>>>> [jar] Building jar:
>>>>>>>
>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
>> b
>>>>>>> uild-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT-sources.jar
>>>>>>>
>>>>>>> set-version:
>>>>>>> [copy] Copying 1 file to
>>>>>>>
>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
>> i
>>>>>>> vy
>>>>>>> [copy] Copying 1 file to
>>>>>>>
>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
>> i
>>>>>>> vy
>>>>>>> [copy] Copying 1 file to
>>>>>>>
>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
>> i
>>>>>>> vy
>>>>>>> [copy] Copying 1 file to
>>>>>>>
>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
>> i
>>>>>>> vy
>>>>>>>
>>>>>>> clean-sign:
>>>>>>>
>>>>>>> sign:
>>>>>>>
>>>>>>> signanddeploy:
>>>>>>>
>>>>>>> simpledeploy:
>>>>>>> [artifact:install-provider] Installing provider:
>>>>>>> org.apache.maven.wagon:wagon-http:jar:1.0-beta-2:runtime
>>>>>>> [artifact:deploy] Deploying to
>>>>>>> https://repository.apache.org/content/repositories/snapshots
>>>>>>> [artifact:deploy] [INFO] Retrieving previous build number from
>>>>>>> apache.snapshots.https
>>>>>>> [artifact:deploy] Uploading:
>>>>>>>
>> org/apache/hadoop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110>>>>>
>> 3
>>>>>>> 03.213523-60.jar to apache.snapshots.https
>>>>>>> [artifact:deploy] Uploaded 1741K
>>>>>>> [artifact:deploy] An error has occurred while processing the Maven
>>>>>>> artifact
>>>>>>> tasks.
>>>>>>> [artifact:deploy] Diagnosis:
>>>>>>> [artifact:deploy]
>>>>>>> [artifact:deploy] Error deploying artifact
>>>>>>> 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to
>>>>>>> transfer file:
>>>>>>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/ha>>>>>
>> d
>>>>>>>
>> oop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.>>>>>
>> j
>>>>>>> ar. Return code is: 401
>>>>>>>
>>>>>>> BUILD FAILED
>>>>>>>
>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
>> b
>>>>>>> uild.xml:1528: Error deploying artifact
>>>>>>> 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to
>>>>>>> transfer file:
>>>>>>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/ha>>>>>
>> d
>>>>>>>
>> oop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.>>>>>
>> j
>>>>>>> ar. Return code is: 401
>>>>>>>
>>>>>>> Total time: 3 minutes 20 seconds
>>>>>>>
>>>>>>>
>>>>>>> ======================================================================
>>>>>>> ======================================================================
>>>>>>> STORE: saving artifacts
>>>>>>> ======================================================================
>>>>>>> ======================================================================
>>>>>>>
>>>>>>>
>>>>>>> mv: cannot stat `build/*.tar.gz': No such file or directory
>>>>>>> mv: cannot stat `build/test/findbugs': No such file or directory
>>>>>>> mv: cannot stat `build/docs/api': No such file or directory
>>>>>>> Build Failed
>>>>>>> [FINDBUGS] Skipping publisher since build result is FAILURE
>>>>>>> Recording fingerprints
>>>>>>> Archiving artifacts
>>>>>>> Recording test results
>>>>>>> Publishing Javadoc
>>>>>>> Publishing Clover coverage report...
>>>>>>> No Clover report will be published due to a Build Failure
>>>>>>> Email was triggered for: Failure
>>>>>>> Sending email for trigger: Failure
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>> ##########################################################################>>>>>
>> #
>>>>>>> ########
>>>>>>> ############################## FAILED TESTS (if any)
>>>>>>> ##############################
>>>>>>> No tests ran.
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Todd Lipcon
>>>>>> Software Engineer, Cloudera
>>>>>>
>>>>>
>>>
>>
>>
>
--
Todd Lipcon
Software Engineer, Cloudera
Re: Hadoop-Mapreduce-trunk-Commit - Build # 621 - Still Failing
Posted by Konstantin Boudnik <co...@apache.org>.
Thanks a lot Giri!
I guess this is another reason to have CM in place for the build machines.
On Fri, Mar 4, 2011 at 16:30, Giridharan Kesavan
<gk...@yahoo-inc.com> wrote:
> It looks like settings.xml file is deleted by someone while cleaning the m2
> repository (my guess). I ve copied it back.
> I'm triggering a build to verify this.
>
> -Giri
>
>
> On 3/4/11 4:21 PM, "Giridharan Kesavan" <gk...@yahoo-inc.com> wrote:
>
>> I'm lookin into it..
>> -Giri
>>
>> On 3/4/11 3:04 PM, "Konstantin Boudnik" <co...@apache.org> wrote:
>>
>>> Looks like the same symptoms are affecting Common trunk builds
>>> https://hudson.apache.org/hudson/job/Hadoop-Common-trunk-Commit/516/
>>> Have our build env. has been changed recently?
>>> --
>>> Take care,
>>> Konstantin (Cos) Boudnik
>>>
>>> On Thu, Mar 3, 2011 at 21:36, Konstantin Boudnik <co...@apache.org> wrote:
>>>> That seems like settings.xml has been modified, but then it'd affect
>>>> other builds as well. Unless we are using different machines/users for
>>>> different component's builds.
>>>>
>>>> On Thu, Mar 3, 2011 at 13:41, Todd Lipcon <to...@cloudera.com> wrote:
>>>>> Anyone understand why we can't seem to publish to apache maven anymore?
>>>>>
>>>>> -Todd
>>>>>
>>>>> On Thu, Mar 3, 2011 at 1:35 PM, Apache Hudson Server
>>>>> <hu...@hudson.apache.org> wrote:
>>>>>> See
>>>>>> https://hudson.apache.org/hudson/job/Hadoop-Mapreduce-trunk-Commit/621/
>>>>>>
>>>>>>
> ##########################################################################>>>>>
> #
>>>>>> ########
>>>>>> ########################## LAST 60 LINES OF THE CONSOLE
>>>>>> ###########################
>>>>>> [...truncated 4464 lines...]
>>>>>> [javac] Compiling 11 source files to
>>>>>>
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
> b
>>>>>> uild-fi/system/test/classes
>>>>>> [javac] Note: Some input files use or override a deprecated API.
>>>>>> [javac] Note: Recompile with -Xlint:deprecation for details.
>>>>>>
>>>>>> jar-test-system:
>>>>>>
>>>>>> -do-jar-test:
>>>>>> [jar] Building jar:
>>>>>>
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
> b
>>>>>> uild-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT.jar
>>>>>> [jar] Building jar:
>>>>>>
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
> b
>>>>>> uild-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT-sources.jar
>>>>>>
>>>>>> set-version:
>>>>>> [copy] Copying 1 file to
>>>>>>
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
> i
>>>>>> vy
>>>>>> [copy] Copying 1 file to
>>>>>>
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
> i
>>>>>> vy
>>>>>> [copy] Copying 1 file to
>>>>>>
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
> i
>>>>>> vy
>>>>>> [copy] Copying 1 file to
>>>>>>
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
> i
>>>>>> vy
>>>>>>
>>>>>> clean-sign:
>>>>>>
>>>>>> sign:
>>>>>>
>>>>>> signanddeploy:
>>>>>>
>>>>>> simpledeploy:
>>>>>> [artifact:install-provider] Installing provider:
>>>>>> org.apache.maven.wagon:wagon-http:jar:1.0-beta-2:runtime
>>>>>> [artifact:deploy] Deploying to
>>>>>> https://repository.apache.org/content/repositories/snapshots
>>>>>> [artifact:deploy] [INFO] Retrieving previous build number from
>>>>>> apache.snapshots.https
>>>>>> [artifact:deploy] Uploading:
>>>>>>
> org/apache/hadoop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110>>>>>
> 3
>>>>>> 03.213523-60.jar to apache.snapshots.https
>>>>>> [artifact:deploy] Uploaded 1741K
>>>>>> [artifact:deploy] An error has occurred while processing the Maven
>>>>>> artifact
>>>>>> tasks.
>>>>>> [artifact:deploy] Diagnosis:
>>>>>> [artifact:deploy]
>>>>>> [artifact:deploy] Error deploying artifact
>>>>>> 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to
>>>>>> transfer file:
>>>>>>
> https://repository.apache.org/content/repositories/snapshots/org/apache/ha>>>>>
> d
>>>>>>
> oop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.>>>>>
> j
>>>>>> ar. Return code is: 401
>>>>>>
>>>>>> BUILD FAILED
>>>>>>
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
> b
>>>>>> uild.xml:1528: Error deploying artifact
>>>>>> 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to
>>>>>> transfer file:
>>>>>>
> https://repository.apache.org/content/repositories/snapshots/org/apache/ha>>>>>
> d
>>>>>>
> oop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.>>>>>
> j
>>>>>> ar. Return code is: 401
>>>>>>
>>>>>> Total time: 3 minutes 20 seconds
>>>>>>
>>>>>>
>>>>>> ======================================================================
>>>>>> ======================================================================
>>>>>> STORE: saving artifacts
>>>>>> ======================================================================
>>>>>> ======================================================================
>>>>>>
>>>>>>
>>>>>> mv: cannot stat `build/*.tar.gz': No such file or directory
>>>>>> mv: cannot stat `build/test/findbugs': No such file or directory
>>>>>> mv: cannot stat `build/docs/api': No such file or directory
>>>>>> Build Failed
>>>>>> [FINDBUGS] Skipping publisher since build result is FAILURE
>>>>>> Recording fingerprints
>>>>>> Archiving artifacts
>>>>>> Recording test results
>>>>>> Publishing Javadoc
>>>>>> Publishing Clover coverage report...
>>>>>> No Clover report will be published due to a Build Failure
>>>>>> Email was triggered for: Failure
>>>>>> Sending email for trigger: Failure
>>>>>>
>>>>>>
>>>>>>
>>>>>>
> ##########################################################################>>>>>
> #
>>>>>> ########
>>>>>> ############################## FAILED TESTS (if any)
>>>>>> ##############################
>>>>>> No tests ran.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Todd Lipcon
>>>>> Software Engineer, Cloudera
>>>>>
>>>>
>>
>
>
Re: Hadoop-Mapreduce-trunk-Commit - Build # 621 - Still Failing
Posted by Konstantin Boudnik <co...@apache.org>.
Thanks a lot Giri!
I guess this is another reason to have CM in place for the build machines.
On Fri, Mar 4, 2011 at 16:30, Giridharan Kesavan
<gk...@yahoo-inc.com> wrote:
> It looks like settings.xml file is deleted by someone while cleaning the m2
> repository (my guess). I ve copied it back.
> I'm triggering a build to verify this.
>
> -Giri
>
>
> On 3/4/11 4:21 PM, "Giridharan Kesavan" <gk...@yahoo-inc.com> wrote:
>
>> I'm lookin into it..
>> -Giri
>>
>> On 3/4/11 3:04 PM, "Konstantin Boudnik" <co...@apache.org> wrote:
>>
>>> Looks like the same symptoms are affecting Common trunk builds
>>> https://hudson.apache.org/hudson/job/Hadoop-Common-trunk-Commit/516/
>>> Have our build env. has been changed recently?
>>> --
>>> Take care,
>>> Konstantin (Cos) Boudnik
>>>
>>> On Thu, Mar 3, 2011 at 21:36, Konstantin Boudnik <co...@apache.org> wrote:
>>>> That seems like settings.xml has been modified, but then it'd affect
>>>> other builds as well. Unless we are using different machines/users for
>>>> different component's builds.
>>>>
>>>> On Thu, Mar 3, 2011 at 13:41, Todd Lipcon <to...@cloudera.com> wrote:
>>>>> Anyone understand why we can't seem to publish to apache maven anymore?
>>>>>
>>>>> -Todd
>>>>>
>>>>> On Thu, Mar 3, 2011 at 1:35 PM, Apache Hudson Server
>>>>> <hu...@hudson.apache.org> wrote:
>>>>>> See
>>>>>> https://hudson.apache.org/hudson/job/Hadoop-Mapreduce-trunk-Commit/621/
>>>>>>
>>>>>>
> ##########################################################################>>>>>
> #
>>>>>> ########
>>>>>> ########################## LAST 60 LINES OF THE CONSOLE
>>>>>> ###########################
>>>>>> [...truncated 4464 lines...]
>>>>>> [javac] Compiling 11 source files to
>>>>>>
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
> b
>>>>>> uild-fi/system/test/classes
>>>>>> [javac] Note: Some input files use or override a deprecated API.
>>>>>> [javac] Note: Recompile with -Xlint:deprecation for details.
>>>>>>
>>>>>> jar-test-system:
>>>>>>
>>>>>> -do-jar-test:
>>>>>> [jar] Building jar:
>>>>>>
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
> b
>>>>>> uild-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT.jar
>>>>>> [jar] Building jar:
>>>>>>
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
> b
>>>>>> uild-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT-sources.jar
>>>>>>
>>>>>> set-version:
>>>>>> [copy] Copying 1 file to
>>>>>>
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
> i
>>>>>> vy
>>>>>> [copy] Copying 1 file to
>>>>>>
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
> i
>>>>>> vy
>>>>>> [copy] Copying 1 file to
>>>>>>
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
> i
>>>>>> vy
>>>>>> [copy] Copying 1 file to
>>>>>>
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
> i
>>>>>> vy
>>>>>>
>>>>>> clean-sign:
>>>>>>
>>>>>> sign:
>>>>>>
>>>>>> signanddeploy:
>>>>>>
>>>>>> simpledeploy:
>>>>>> [artifact:install-provider] Installing provider:
>>>>>> org.apache.maven.wagon:wagon-http:jar:1.0-beta-2:runtime
>>>>>> [artifact:deploy] Deploying to
>>>>>> https://repository.apache.org/content/repositories/snapshots
>>>>>> [artifact:deploy] [INFO] Retrieving previous build number from
>>>>>> apache.snapshots.https
>>>>>> [artifact:deploy] Uploading:
>>>>>>
> org/apache/hadoop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110>>>>>
> 3
>>>>>> 03.213523-60.jar to apache.snapshots.https
>>>>>> [artifact:deploy] Uploaded 1741K
>>>>>> [artifact:deploy] An error has occurred while processing the Maven
>>>>>> artifact
>>>>>> tasks.
>>>>>> [artifact:deploy] Diagnosis:
>>>>>> [artifact:deploy]
>>>>>> [artifact:deploy] Error deploying artifact
>>>>>> 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to
>>>>>> transfer file:
>>>>>>
> https://repository.apache.org/content/repositories/snapshots/org/apache/ha>>>>>
> d
>>>>>>
> oop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.>>>>>
> j
>>>>>> ar. Return code is: 401
>>>>>>
>>>>>> BUILD FAILED
>>>>>>
> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
> b
>>>>>> uild.xml:1528: Error deploying artifact
>>>>>> 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to
>>>>>> transfer file:
>>>>>>
> https://repository.apache.org/content/repositories/snapshots/org/apache/ha>>>>>
> d
>>>>>>
> oop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.>>>>>
> j
>>>>>> ar. Return code is: 401
>>>>>>
>>>>>> Total time: 3 minutes 20 seconds
>>>>>>
>>>>>>
>>>>>> ======================================================================
>>>>>> ======================================================================
>>>>>> STORE: saving artifacts
>>>>>> ======================================================================
>>>>>> ======================================================================
>>>>>>
>>>>>>
>>>>>> mv: cannot stat `build/*.tar.gz': No such file or directory
>>>>>> mv: cannot stat `build/test/findbugs': No such file or directory
>>>>>> mv: cannot stat `build/docs/api': No such file or directory
>>>>>> Build Failed
>>>>>> [FINDBUGS] Skipping publisher since build result is FAILURE
>>>>>> Recording fingerprints
>>>>>> Archiving artifacts
>>>>>> Recording test results
>>>>>> Publishing Javadoc
>>>>>> Publishing Clover coverage report...
>>>>>> No Clover report will be published due to a Build Failure
>>>>>> Email was triggered for: Failure
>>>>>> Sending email for trigger: Failure
>>>>>>
>>>>>>
>>>>>>
>>>>>>
> ##########################################################################>>>>>
> #
>>>>>> ########
>>>>>> ############################## FAILED TESTS (if any)
>>>>>> ##############################
>>>>>> No tests ran.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Todd Lipcon
>>>>> Software Engineer, Cloudera
>>>>>
>>>>
>>
>
>
Re: Hadoop-Mapreduce-trunk-Commit - Build # 621 - Still Failing
Posted by Giridharan Kesavan <gk...@yahoo-inc.com>.
It looks like settings.xml file is deleted by someone while cleaning the m2
repository (my guess). I ve copied it back.
I'm triggering a build to verify this.
-Giri
On 3/4/11 4:21 PM, "Giridharan Kesavan" <gk...@yahoo-inc.com> wrote:
> I'm lookin into it..
> -Giri
>
> On 3/4/11 3:04 PM, "Konstantin Boudnik" <co...@apache.org> wrote:
>
>> Looks like the same symptoms are affecting Common trunk builds
>> https://hudson.apache.org/hudson/job/Hadoop-Common-trunk-Commit/516/
>> Have our build env. has been changed recently?
>> --
>> Take care,
>> Konstantin (Cos) Boudnik
>>
>> On Thu, Mar 3, 2011 at 21:36, Konstantin Boudnik <co...@apache.org> wrote:
>>> That seems like settings.xml has been modified, but then it'd affect
>>> other builds as well. Unless we are using different machines/users for
>>> different component's builds.
>>>
>>> On Thu, Mar 3, 2011 at 13:41, Todd Lipcon <to...@cloudera.com> wrote:
>>>> Anyone understand why we can't seem to publish to apache maven anymore?
>>>>
>>>> -Todd
>>>>
>>>> On Thu, Mar 3, 2011 at 1:35 PM, Apache Hudson Server
>>>> <hu...@hudson.apache.org> wrote:
>>>>> See
>>>>> https://hudson.apache.org/hudson/job/Hadoop-Mapreduce-trunk-Commit/621/
>>>>>
>>>>>
##########################################################################>>>>>
#
>>>>> ########
>>>>> ########################## LAST 60 LINES OF THE CONSOLE
>>>>> ###########################
>>>>> [...truncated 4464 lines...]
>>>>> [javac] Compiling 11 source files to
>>>>>
/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
b
>>>>> uild-fi/system/test/classes
>>>>> [javac] Note: Some input files use or override a deprecated API.
>>>>> [javac] Note: Recompile with -Xlint:deprecation for details.
>>>>>
>>>>> jar-test-system:
>>>>>
>>>>> -do-jar-test:
>>>>> [jar] Building jar:
>>>>>
/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
b
>>>>> uild-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT.jar
>>>>> [jar] Building jar:
>>>>>
/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
b
>>>>> uild-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT-sources.jar
>>>>>
>>>>> set-version:
>>>>> [copy] Copying 1 file to
>>>>>
/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
i
>>>>> vy
>>>>> [copy] Copying 1 file to
>>>>>
/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
i
>>>>> vy
>>>>> [copy] Copying 1 file to
>>>>>
/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
i
>>>>> vy
>>>>> [copy] Copying 1 file to
>>>>>
/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
i
>>>>> vy
>>>>>
>>>>> clean-sign:
>>>>>
>>>>> sign:
>>>>>
>>>>> signanddeploy:
>>>>>
>>>>> simpledeploy:
>>>>> [artifact:install-provider] Installing provider:
>>>>> org.apache.maven.wagon:wagon-http:jar:1.0-beta-2:runtime
>>>>> [artifact:deploy] Deploying to
>>>>> https://repository.apache.org/content/repositories/snapshots
>>>>> [artifact:deploy] [INFO] Retrieving previous build number from
>>>>> apache.snapshots.https
>>>>> [artifact:deploy] Uploading:
>>>>>
org/apache/hadoop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110>>>>>
3
>>>>> 03.213523-60.jar to apache.snapshots.https
>>>>> [artifact:deploy] Uploaded 1741K
>>>>> [artifact:deploy] An error has occurred while processing the Maven
>>>>> artifact
>>>>> tasks.
>>>>> [artifact:deploy] Diagnosis:
>>>>> [artifact:deploy]
>>>>> [artifact:deploy] Error deploying artifact
>>>>> 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to
>>>>> transfer file:
>>>>>
https://repository.apache.org/content/repositories/snapshots/org/apache/ha>>>>>
d
>>>>>
oop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.>>>>>
j
>>>>> ar. Return code is: 401
>>>>>
>>>>> BUILD FAILED
>>>>>
/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
b
>>>>> uild.xml:1528: Error deploying artifact
>>>>> 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to
>>>>> transfer file:
>>>>>
https://repository.apache.org/content/repositories/snapshots/org/apache/ha>>>>>
d
>>>>>
oop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.>>>>>
j
>>>>> ar. Return code is: 401
>>>>>
>>>>> Total time: 3 minutes 20 seconds
>>>>>
>>>>>
>>>>> ======================================================================
>>>>> ======================================================================
>>>>> STORE: saving artifacts
>>>>> ======================================================================
>>>>> ======================================================================
>>>>>
>>>>>
>>>>> mv: cannot stat `build/*.tar.gz': No such file or directory
>>>>> mv: cannot stat `build/test/findbugs': No such file or directory
>>>>> mv: cannot stat `build/docs/api': No such file or directory
>>>>> Build Failed
>>>>> [FINDBUGS] Skipping publisher since build result is FAILURE
>>>>> Recording fingerprints
>>>>> Archiving artifacts
>>>>> Recording test results
>>>>> Publishing Javadoc
>>>>> Publishing Clover coverage report...
>>>>> No Clover report will be published due to a Build Failure
>>>>> Email was triggered for: Failure
>>>>> Sending email for trigger: Failure
>>>>>
>>>>>
>>>>>
>>>>>
##########################################################################>>>>>
#
>>>>> ########
>>>>> ############################## FAILED TESTS (if any)
>>>>> ##############################
>>>>> No tests ran.
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Todd Lipcon
>>>> Software Engineer, Cloudera
>>>>
>>>
>
Re: Hadoop-Mapreduce-trunk-Commit - Build # 621 - Still Failing
Posted by Giridharan Kesavan <gk...@yahoo-inc.com>.
It looks like settings.xml file is deleted by someone while cleaning the m2
repository (my guess). I ve copied it back.
I'm triggering a build to verify this.
-Giri
On 3/4/11 4:21 PM, "Giridharan Kesavan" <gk...@yahoo-inc.com> wrote:
> I'm lookin into it..
> -Giri
>
> On 3/4/11 3:04 PM, "Konstantin Boudnik" <co...@apache.org> wrote:
>
>> Looks like the same symptoms are affecting Common trunk builds
>> https://hudson.apache.org/hudson/job/Hadoop-Common-trunk-Commit/516/
>> Have our build env. has been changed recently?
>> --
>> Take care,
>> Konstantin (Cos) Boudnik
>>
>> On Thu, Mar 3, 2011 at 21:36, Konstantin Boudnik <co...@apache.org> wrote:
>>> That seems like settings.xml has been modified, but then it'd affect
>>> other builds as well. Unless we are using different machines/users for
>>> different component's builds.
>>>
>>> On Thu, Mar 3, 2011 at 13:41, Todd Lipcon <to...@cloudera.com> wrote:
>>>> Anyone understand why we can't seem to publish to apache maven anymore?
>>>>
>>>> -Todd
>>>>
>>>> On Thu, Mar 3, 2011 at 1:35 PM, Apache Hudson Server
>>>> <hu...@hudson.apache.org> wrote:
>>>>> See
>>>>> https://hudson.apache.org/hudson/job/Hadoop-Mapreduce-trunk-Commit/621/
>>>>>
>>>>>
##########################################################################>>>>>
#
>>>>> ########
>>>>> ########################## LAST 60 LINES OF THE CONSOLE
>>>>> ###########################
>>>>> [...truncated 4464 lines...]
>>>>> [javac] Compiling 11 source files to
>>>>>
/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
b
>>>>> uild-fi/system/test/classes
>>>>> [javac] Note: Some input files use or override a deprecated API.
>>>>> [javac] Note: Recompile with -Xlint:deprecation for details.
>>>>>
>>>>> jar-test-system:
>>>>>
>>>>> -do-jar-test:
>>>>> [jar] Building jar:
>>>>>
/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
b
>>>>> uild-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT.jar
>>>>> [jar] Building jar:
>>>>>
/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
b
>>>>> uild-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT-sources.jar
>>>>>
>>>>> set-version:
>>>>> [copy] Copying 1 file to
>>>>>
/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
i
>>>>> vy
>>>>> [copy] Copying 1 file to
>>>>>
/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
i
>>>>> vy
>>>>> [copy] Copying 1 file to
>>>>>
/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
i
>>>>> vy
>>>>> [copy] Copying 1 file to
>>>>>
/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
i
>>>>> vy
>>>>>
>>>>> clean-sign:
>>>>>
>>>>> sign:
>>>>>
>>>>> signanddeploy:
>>>>>
>>>>> simpledeploy:
>>>>> [artifact:install-provider] Installing provider:
>>>>> org.apache.maven.wagon:wagon-http:jar:1.0-beta-2:runtime
>>>>> [artifact:deploy] Deploying to
>>>>> https://repository.apache.org/content/repositories/snapshots
>>>>> [artifact:deploy] [INFO] Retrieving previous build number from
>>>>> apache.snapshots.https
>>>>> [artifact:deploy] Uploading:
>>>>>
org/apache/hadoop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110>>>>>
3
>>>>> 03.213523-60.jar to apache.snapshots.https
>>>>> [artifact:deploy] Uploaded 1741K
>>>>> [artifact:deploy] An error has occurred while processing the Maven
>>>>> artifact
>>>>> tasks.
>>>>> [artifact:deploy] Diagnosis:
>>>>> [artifact:deploy]
>>>>> [artifact:deploy] Error deploying artifact
>>>>> 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to
>>>>> transfer file:
>>>>>
https://repository.apache.org/content/repositories/snapshots/org/apache/ha>>>>>
d
>>>>>
oop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.>>>>>
j
>>>>> ar. Return code is: 401
>>>>>
>>>>> BUILD FAILED
>>>>>
/grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/>>>>>
b
>>>>> uild.xml:1528: Error deploying artifact
>>>>> 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to
>>>>> transfer file:
>>>>>
https://repository.apache.org/content/repositories/snapshots/org/apache/ha>>>>>
d
>>>>>
oop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.>>>>>
j
>>>>> ar. Return code is: 401
>>>>>
>>>>> Total time: 3 minutes 20 seconds
>>>>>
>>>>>
>>>>> ======================================================================
>>>>> ======================================================================
>>>>> STORE: saving artifacts
>>>>> ======================================================================
>>>>> ======================================================================
>>>>>
>>>>>
>>>>> mv: cannot stat `build/*.tar.gz': No such file or directory
>>>>> mv: cannot stat `build/test/findbugs': No such file or directory
>>>>> mv: cannot stat `build/docs/api': No such file or directory
>>>>> Build Failed
>>>>> [FINDBUGS] Skipping publisher since build result is FAILURE
>>>>> Recording fingerprints
>>>>> Archiving artifacts
>>>>> Recording test results
>>>>> Publishing Javadoc
>>>>> Publishing Clover coverage report...
>>>>> No Clover report will be published due to a Build Failure
>>>>> Email was triggered for: Failure
>>>>> Sending email for trigger: Failure
>>>>>
>>>>>
>>>>>
>>>>>
##########################################################################>>>>>
#
>>>>> ########
>>>>> ############################## FAILED TESTS (if any)
>>>>> ##############################
>>>>> No tests ran.
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Todd Lipcon
>>>> Software Engineer, Cloudera
>>>>
>>>
>
Re: Hadoop-Mapreduce-trunk-Commit - Build # 621 - Still Failing
Posted by Giridharan Kesavan <gk...@yahoo-inc.com>.
I'm lookin into it..
-Giri
On 3/4/11 3:04 PM, "Konstantin Boudnik" <co...@apache.org> wrote:
> Looks like the same symptoms are affecting Common trunk builds
> https://hudson.apache.org/hudson/job/Hadoop-Common-trunk-Commit/516/
> Have our build env. has been changed recently?
> --
> Take care,
> Konstantin (Cos) Boudnik
>
> On Thu, Mar 3, 2011 at 21:36, Konstantin Boudnik <co...@apache.org> wrote:
>> That seems like settings.xml has been modified, but then it'd affect
>> other builds as well. Unless we are using different machines/users for
>> different component's builds.
>>
>> On Thu, Mar 3, 2011 at 13:41, Todd Lipcon <to...@cloudera.com> wrote:
>>> Anyone understand why we can't seem to publish to apache maven anymore?
>>>
>>> -Todd
>>>
>>> On Thu, Mar 3, 2011 at 1:35 PM, Apache Hudson Server
>>> <hu...@hudson.apache.org> wrote:
>>>> See https://hudson.apache.org/hudson/job/Hadoop-Mapreduce-trunk-Commit/621/
>>>>
>>>> ###########################################################################
>>>> ########
>>>> ########################## LAST 60 LINES OF THE CONSOLE
>>>> ###########################
>>>> [...truncated 4464 lines...]
>>>> [javac] Compiling 11 source files to
>>>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/b
>>>> uild-fi/system/test/classes
>>>> [javac] Note: Some input files use or override a deprecated API.
>>>> [javac] Note: Recompile with -Xlint:deprecation for details.
>>>>
>>>> jar-test-system:
>>>>
>>>> -do-jar-test:
>>>> [jar] Building jar:
>>>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/b
>>>> uild-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT.jar
>>>> [jar] Building jar:
>>>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/b
>>>> uild-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT-sources.jar
>>>>
>>>> set-version:
>>>> [copy] Copying 1 file to
>>>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/i
>>>> vy
>>>> [copy] Copying 1 file to
>>>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/i
>>>> vy
>>>> [copy] Copying 1 file to
>>>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/i
>>>> vy
>>>> [copy] Copying 1 file to
>>>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/i
>>>> vy
>>>>
>>>> clean-sign:
>>>>
>>>> sign:
>>>>
>>>> signanddeploy:
>>>>
>>>> simpledeploy:
>>>> [artifact:install-provider] Installing provider:
>>>> org.apache.maven.wagon:wagon-http:jar:1.0-beta-2:runtime
>>>> [artifact:deploy] Deploying to
>>>> https://repository.apache.org/content/repositories/snapshots
>>>> [artifact:deploy] [INFO] Retrieving previous build number from
>>>> apache.snapshots.https
>>>> [artifact:deploy] Uploading:
>>>> org/apache/hadoop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-201103
>>>> 03.213523-60.jar to apache.snapshots.https
>>>> [artifact:deploy] Uploaded 1741K
>>>> [artifact:deploy] An error has occurred while processing the Maven artifact
>>>> tasks.
>>>> [artifact:deploy] Diagnosis:
>>>> [artifact:deploy]
>>>> [artifact:deploy] Error deploying artifact
>>>> 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to
>>>> transfer file:
>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/had
>>>> oop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.j
>>>> ar. Return code is: 401
>>>>
>>>> BUILD FAILED
>>>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/b
>>>> uild.xml:1528: Error deploying artifact
>>>> 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to
>>>> transfer file:
>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/had
>>>> oop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.j
>>>> ar. Return code is: 401
>>>>
>>>> Total time: 3 minutes 20 seconds
>>>>
>>>>
>>>> ======================================================================
>>>> ======================================================================
>>>> STORE: saving artifacts
>>>> ======================================================================
>>>> ======================================================================
>>>>
>>>>
>>>> mv: cannot stat `build/*.tar.gz': No such file or directory
>>>> mv: cannot stat `build/test/findbugs': No such file or directory
>>>> mv: cannot stat `build/docs/api': No such file or directory
>>>> Build Failed
>>>> [FINDBUGS] Skipping publisher since build result is FAILURE
>>>> Recording fingerprints
>>>> Archiving artifacts
>>>> Recording test results
>>>> Publishing Javadoc
>>>> Publishing Clover coverage report...
>>>> No Clover report will be published due to a Build Failure
>>>> Email was triggered for: Failure
>>>> Sending email for trigger: Failure
>>>>
>>>>
>>>>
>>>> ###########################################################################
>>>> ########
>>>> ############################## FAILED TESTS (if any)
>>>> ##############################
>>>> No tests ran.
>>>>
>>>
>>>
>>>
>>> --
>>> Todd Lipcon
>>> Software Engineer, Cloudera
>>>
>>
Re: Hadoop-Mapreduce-trunk-Commit - Build # 621 - Still Failing
Posted by Giridharan Kesavan <gk...@yahoo-inc.com>.
I'm lookin into it..
-Giri
On 3/4/11 3:04 PM, "Konstantin Boudnik" <co...@apache.org> wrote:
> Looks like the same symptoms are affecting Common trunk builds
> https://hudson.apache.org/hudson/job/Hadoop-Common-trunk-Commit/516/
> Have our build env. has been changed recently?
> --
> Take care,
> Konstantin (Cos) Boudnik
>
> On Thu, Mar 3, 2011 at 21:36, Konstantin Boudnik <co...@apache.org> wrote:
>> That seems like settings.xml has been modified, but then it'd affect
>> other builds as well. Unless we are using different machines/users for
>> different component's builds.
>>
>> On Thu, Mar 3, 2011 at 13:41, Todd Lipcon <to...@cloudera.com> wrote:
>>> Anyone understand why we can't seem to publish to apache maven anymore?
>>>
>>> -Todd
>>>
>>> On Thu, Mar 3, 2011 at 1:35 PM, Apache Hudson Server
>>> <hu...@hudson.apache.org> wrote:
>>>> See https://hudson.apache.org/hudson/job/Hadoop-Mapreduce-trunk-Commit/621/
>>>>
>>>> ###########################################################################
>>>> ########
>>>> ########################## LAST 60 LINES OF THE CONSOLE
>>>> ###########################
>>>> [...truncated 4464 lines...]
>>>> [javac] Compiling 11 source files to
>>>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/b
>>>> uild-fi/system/test/classes
>>>> [javac] Note: Some input files use or override a deprecated API.
>>>> [javac] Note: Recompile with -Xlint:deprecation for details.
>>>>
>>>> jar-test-system:
>>>>
>>>> -do-jar-test:
>>>> [jar] Building jar:
>>>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/b
>>>> uild-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT.jar
>>>> [jar] Building jar:
>>>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/b
>>>> uild-fi/system/hadoop-mapred-instrumented-test-0.23.0-SNAPSHOT-sources.jar
>>>>
>>>> set-version:
>>>> [copy] Copying 1 file to
>>>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/i
>>>> vy
>>>> [copy] Copying 1 file to
>>>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/i
>>>> vy
>>>> [copy] Copying 1 file to
>>>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/i
>>>> vy
>>>> [copy] Copying 1 file to
>>>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/i
>>>> vy
>>>>
>>>> clean-sign:
>>>>
>>>> sign:
>>>>
>>>> signanddeploy:
>>>>
>>>> simpledeploy:
>>>> [artifact:install-provider] Installing provider:
>>>> org.apache.maven.wagon:wagon-http:jar:1.0-beta-2:runtime
>>>> [artifact:deploy] Deploying to
>>>> https://repository.apache.org/content/repositories/snapshots
>>>> [artifact:deploy] [INFO] Retrieving previous build number from
>>>> apache.snapshots.https
>>>> [artifact:deploy] Uploading:
>>>> org/apache/hadoop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-201103
>>>> 03.213523-60.jar to apache.snapshots.https
>>>> [artifact:deploy] Uploaded 1741K
>>>> [artifact:deploy] An error has occurred while processing the Maven artifact
>>>> tasks.
>>>> [artifact:deploy] Diagnosis:
>>>> [artifact:deploy]
>>>> [artifact:deploy] Error deploying artifact
>>>> 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to
>>>> transfer file:
>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/had
>>>> oop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.j
>>>> ar. Return code is: 401
>>>>
>>>> BUILD FAILED
>>>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk-Commit/trunk/b
>>>> uild.xml:1528: Error deploying artifact
>>>> 'org.apache.hadoop:hadoop-mapred:jar': Error deploying artifact: Failed to
>>>> transfer file:
>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/had
>>>> oop/hadoop-mapred/0.23.0-SNAPSHOT/hadoop-mapred-0.23.0-20110303.213523-60.j
>>>> ar. Return code is: 401
>>>>
>>>> Total time: 3 minutes 20 seconds
>>>>
>>>>
>>>> ======================================================================
>>>> ======================================================================
>>>> STORE: saving artifacts
>>>> ======================================================================
>>>> ======================================================================
>>>>
>>>>
>>>> mv: cannot stat `build/*.tar.gz': No such file or directory
>>>> mv: cannot stat `build/test/findbugs': No such file or directory
>>>> mv: cannot stat `build/docs/api': No such file or directory
>>>> Build Failed
>>>> [FINDBUGS] Skipping publisher since build result is FAILURE
>>>> Recording fingerprints
>>>> Archiving artifacts
>>>> Recording test results
>>>> Publishing Javadoc
>>>> Publishing Clover coverage report...
>>>> No Clover report will be published due to a Build Failure
>>>> Email was triggered for: Failure
>>>> Sending email for trigger: Failure
>>>>
>>>>
>>>>
>>>> ###########################################################################
>>>> ########
>>>> ############################## FAILED TESTS (if any)
>>>> ##############################
>>>> No tests ran.
>>>>
>>>
>>>
>>>
>>> --
>>> Todd Lipcon
>>> Software Engineer, Cloudera
>>>
>>