Well it looks like a configuration bug:

Ivy supports locking for this:
http://ant.apache.org/ivy/history/latest-milestone/settings/lock-strategies.html

But the default is "no-lock"
http://ant.apache.org/ivy/history/latest-milestone/settings/caches.html

I think we should investigate fixing lucene/ivy-settings.xml to use
locking? failures like this are annoying

On Fri, Oct 5, 2012 at 4:17 PM, Dawid Weiss
<[email protected]> wrote:
> This looks like an ivy bug to me -- seems to be overwriting the same
> cache file so one of the parsers fails.
>
> Dawid
>
> On Fri, Oct 5, 2012 at 10:14 PM, Robert Muir <[email protected]> wrote:
>> On Fri, Oct 5, 2012 at 4:08 PM,  <[email protected]> wrote:
>>> BUILD FAILED
>>> <http://sierranevada.servebeer.com/job/lucene40-beaster/ws/build.xml>:49: 
>>> The following error occurred while executing this line:
>>> <http://sierranevada.servebeer.com/job/lucene40-beaster/ws/common-build.xml>:643:
>>>  The following error occurred while executing this line:
>>> <http://sierranevada.servebeer.com/job/lucene40-beaster/ws/common-build.xml>:292:
>>>  impossible to ivy retrieve: java.lang.RuntimeException: problem during 
>>> retrieve of org.apache.lucene#core-test-framework: 
>>> java.text.ParseException: failed to parse report: 
>>> /home/rmuir/.ivy2/cache/org.apache.lucene-core-test-framework-default.xml: 
>>> Premature end of file.
>>>         at 
>>> org.apache.ivy.core.retrieve.RetrieveEngine.retrieve(RetrieveEngine.java:206)
>>
>> I've seen this a few times before, this is some bug in ivy (or the
>> cache needs a different locking setup or something i dont understand).
>>
>> This probably happened because I'm also running 'ant test
>> -Dtestcase=XXXX -Dtestmethod=YYYY' in a shellscript in a loop 1000
>> times separately in another checkout on this machine.
>>
>> ---------------------------------------------------------------------
>> 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]
>

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

Reply via email to