...
de65b45fca00445d5dde8f25ee5bc67f791a84f7
a61c9f2c22362692b47e4d38dd32953f3a7156d1
: Date: Sun, 9 Dec 2018 11:12:27 -0500
: From: Steve Rowe
: Reply-To: dev@lucene.apache.org
: To: Lucene Dev
: Subject: Re: [JENKINS] Lucene-Solr-NightlyTests-7.x - Build # 399 - Still
: Failing
:
: Yet again
I wonder what this is. Looks like something is doing a *lot* of
writing... strange.
D.
On Sun, Dec 9, 2018 at 6:59 PM Steve Rowe wrote:
>
> Hi Dawid,
>
> Unfortunately I haven't captured any of the .spill or .events files. If it
> happens again I will.
>
> Steve
>
> > On Dec 9, 2018, at 12:51
Hi Dawid,
Unfortunately I haven't captured any of the .spill or .events files. If it
happens again I will.
Steve
> On Dec 9, 2018, at 12:51 PM, Dawid Weiss wrote:
>
> Hi Steve!
>
>> -rw--- 1 jenkins jenkins 16690023845 Dec 8 14:16
>>
Hi Steve!
> -rw--- 1 jenkins jenkins 16690023845 Dec 8 14:16
> junit4-J0-20181207_213237_5283940733299267111752.spill
> -rw--- 1 jenkins jenkins 18444929688 Dec 8 14:16
> junit4-J0-20181207_213237_5284750168668511801086.events
It looks like JVM output (or process output). Can you cat
Yet again with the huge dump files taking up all available disk space.
I cleaned up the offending workspace, this time on lucene2-us-west.apache.org
(previous occurrences were on lucene1-us-west.apache.org).
Short term, I'm planning on adding a build step to Nightly jobs that deletes
.spill
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-7.x/399/
All tests passed
Build Log:
[...truncated 851 lines...]
[junit4] JVM J0: stderr was not empty, see:
