www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jarek Jarcec Cecho <jar...@apache.org>
Subject Re: What is the process of reporting dead slaves
Date Fri, 21 Aug 2015 16:56:36 GMT
Got it, it looks much better now - thank you!

Jarcec

> On Aug 21, 2015, at 9:33 AM, Andrew Bayer <andrew.bayer@gmail.com> wrote:
> 
> It's not the slaves, it's the master itself.
> 
> A.
> 
> On Fri, Aug 21, 2015 at 12:32 PM, Jarek Jarcec Cecho <jarcec@apache.org>
> wrote:
> 
>> Thanks Andrew!
>> 
>> Just to give you heads up - it just seems that the build slaves went out
>> of disk space as I see this exception:
>> 
>> java.io.IOException: No space left on device
>> 
>> (probably some rogue job or something)
>> 
>> Jarcec
>> 
>>> On Aug 21, 2015, at 9:18 AM, Andrew Bayer <andrew.bayer@gmail.com>
>> wrote:
>>> 
>>> I'll take a look in 30 minutes or so.
>>> On Aug 21, 2015 12:05, "Jarek Jarcec Cecho" <jarcec@apache.org> wrote:
>>> 
>>>> Looking at Jenkins queue - there is 132 queued jobs and only 4 working
>>>> executors :) All the others are marked as “DEAD”.
>>>> 
>>>> I’m wondering what is the process of reporting that? Should I create
>>>> BUILDS or INFRA JIRA, or just send email to this group or something
>>>> completely else?
>>>> 
>>>> Jarcec
>> 
>> 


Mime
View raw message