Thanks Steve!

What a confusing way for ant to try to tell us disk was full :)

Mike McCandless

http://blog.mikemccandless.com


On Fri, Feb 10, 2017 at 5:32 PM, Steve Rowe <[email protected]> wrote:
> I mentioned the issue on Infra hipchat channel, and pono looked and then 
> wrote:
>
>> cleared 9gb in /var/cache/apt/
>
> He also mentioned he’d look further for other culprits, but at least for now 
> things should be okay.
>
> --
> Steve
> www.lucidworks.com
>
>> On Feb 10, 2017, at 1:14 PM, Steve Rowe <[email protected]> wrote:
>>
>> Looks like there are disk space problems.
>>
>> I logged into lucene1-us-west.apache.org and ran ‘df -k /‘:
>>
>> -----
>> $ df -k /
>> Filesystem                             1K-blocks     Used Available Use% 
>> Mounted on
>> /dev/mapper/lucene1--us--west--vg-root  30582652 30566212         0 100% /
>> -----
>>
>> Also from the build log:
>>
>> -----
>> Java HotSpot(TM) 64-Bit Server VM warning: Insufficient space for shared 
>> memory file:
>>   28826
>> Try using the -Djava.io.tmpdir= option to select an alternate temp location.
>> -----
>>
>> --
>> Steve
>> www.lucidworks.com
>>
>>> On Feb 10, 2017, at 10:53 AM, Michael McCandless 
>>> <[email protected]> wrote:
>>>
>>> Maybe we should open an INFRA issue?
>>>
>>> Mike McCandless
>>>
>>> http://blog.mikemccandless.com
>>>
>>>
>>> On Fri, Feb 10, 2017 at 12:21 PM, Adrien Grand <[email protected]> wrote:
>>>> This seems to only affect the Apache Jenkins instances, in case that helps
>>>> someone understand the issue.
>>>>
>>>> Le ven. 10 févr. 2017 à 15:25, Adrien Grand <[email protected]> a écrit :
>>>>>
>>>>> Does anyone have a clue why fixcrlf suddenly started failing?
>>>>>
>>>>> Le ven. 10 févr. 2017 à 14:14, Apache Jenkins Server
>>>>> <[email protected]> a écrit :
>>>>>>
>>>>>> Build: https://builds.apache.org/job/Lucene-Solr-Maven-master/1954/
>>>>>>
>>>>>> No tests ran.
>>>>>>
>>>>>> Build Log:
>>>>>> [...truncated 6831 lines...]
>>>>>> BUILD FAILED
>>>>>>
>>>>>> /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-master/build.xml:793:
>>>>>> The following error occurred while executing this line:
>>>>>>
>>>>>> /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-master/build.xml:326:
>>>>>> The following error occurred while executing this line:
>>>>>>
>>>>>> /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-master/lucene/common-build.xml:533:
>>>>>> The following error occurred while executing this line:
>>>>>>
>>>>>> /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-master/lucene/common-build.xml:528:
>>>>>> The following error occurred while executing this line:
>>>>>>
>>>>>> /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-master/lucene/common-build.xml:746:
>>>>>> The following error occurred while executing this line:
>>>>>>
>>>>>> /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-master/lucene/core/build.xml:54:
>>>>>> The following error occurred while executing this line:
>>>>>>
>>>>>> /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-master/lucene/common-build.xml:2138:
>>>>>> error running fixcrlf on file
>>>>>> /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-master/lucene/build/docs/core/script.js
>>>>>>
>>>>>> Total time: 1 minute 23 seconds
>>>>>> Build step 'Invoke Ant' marked build as failure
>>>>>> 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]
>>>
>>
>
>
> ---------------------------------------------------------------------
> 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