Looks like lingering .lck files in the the Ivy cache from an interrupted build. 
 I’ll work on cleaning it up.

--
Steve
www.lucidworks.com

> On Nov 1, 2017, at 3:43 PM, Apache Jenkins Server <[email protected]> 
> wrote:
> 
> Build: https://builds.apache.org/job/Solr-Artifacts-7.x/75/
> 
> No tests ran.
> 
> Build Log:
> [...truncated 3209 lines...]
> BUILD FAILED
> /x1/jenkins/jenkins-slave/workspace/Solr-Artifacts-7.x/solr/build.xml:549: 
> The following error occurred while executing this line:
> /x1/jenkins/jenkins-slave/workspace/Solr-Artifacts-7.x/solr/build.xml:451: 
> The following error occurred while executing this line:
> /x1/jenkins/jenkins-slave/workspace/Solr-Artifacts-7.x/solr/test-framework/build.xml:97:
>  The following error occurred while executing this line:
> /x1/jenkins/jenkins-slave/workspace/Solr-Artifacts-7.x/lucene/common-build.xml:556:
>  The following error occurred while executing this line:
> /x1/jenkins/jenkins-slave/workspace/Solr-Artifacts-7.x/lucene/common-build.xml:551:
>  The following error occurred while executing this line:
> /x1/jenkins/jenkins-slave/workspace/Solr-Artifacts-7.x/lucene/build.xml:484: 
> The following error occurred while executing this line:
> /x1/jenkins/jenkins-slave/workspace/Solr-Artifacts-7.x/lucene/common-build.xml:2262:
>  The following error occurred while executing this line:
> /x1/jenkins/jenkins-slave/workspace/Solr-Artifacts-7.x/lucene/common-build.xml:409:
>  impossible to resolve dependencies:
>       resolve failed - see output for details
> 
> Total time: 25 minutes 47 seconds
> Build step 'Invoke Ant' marked build as failure
> Archiving artifacts
> 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