This is pretty strange - I looked on lucene1-us-west.apache.org, and the 
lucene/build/lucene.tgz.unpacked/ directory does not exist.

The trunk version of this job has succeeded twice on ASF Jenkins.

I just locally ran ‘ant prepare-release-no-sign’ on branch_5x under lucene/ and 
it built successfully, so AFAICT there is no svn->git build problem here.

The Solr-Artifacts-5.x job has not yet run on ASF Jenkins since the git move, 
but the trunk version has, successfully.

> On Jan 26, 2016, at 4:54 AM, Apache Jenkins Server 
> <[email protected]> wrote:
> 
> Build: https://builds.apache.org/job/Lucene-Artifacts-5.x/1074/
> 
> No tests ran.
> 
> Build Log:
> [...truncated 7348 lines...]
> BUILD FAILED
> /x1/jenkins/jenkins-slave/workspace/Lucene-Artifacts-5.x/lucene/build.xml:427:
>  The following error occurred while executing this line:
> /x1/jenkins/jenkins-slave/workspace/Lucene-Artifacts-5.x/lucene/build.xml:415:
>  The following error occurred while executing this line:
> /x1/jenkins/jenkins-slave/workspace/Lucene-Artifacts-5.x/lucene/common-build.xml:1691:
>  The following error occurred while executing this line:
> /x1/jenkins/jenkins-slave/workspace/Lucene-Artifacts-5.x/lucene/common-build.xml:575:
>  Error installing artifact 'org.apache.lucene:lucene-core:jar': Error 
> installing artifact: File 
> /x1/jenkins/jenkins-slave/workspace/Lucene-Artifacts-5.x/lucene/build/lucene.tgz.unpacked/lucene-5.5.0-1074/core/lucene-core-5.5.0-1074.jar
>  does not exist
> 
> Total time: 4 minutes 53 seconds
> Build step 'Invoke Ant' marked build as failure
> Archiving artifacts
> Compressed 167.56 MB of artifacts by 19.7% relative to #1073
> Publishing Javadoc
> Email was triggered for: Failure - Any
> Sending email for trigger: Failure - Any
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to