hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Boudnik <...@apache.org>
Subject Re: Hadoop-Mapreduce-trunk-Commit - Build # 621 - Still Failing
Date Fri, 04 Mar 2011 05:36:18 GMT
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 <todd@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
> <hudson@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
>

Mime
View raw message