Still seeing no space left on device errors on jenkins-7 (for example:
https://builds.apache.org/job/beam_PreCommit_PythonLint_Commit/2754/)


On Fri, Mar 6, 2020 at 7:11 PM Alan Myrvold <[email protected]> wrote:

> Did a one time cleanup of tmp files owned by jenkins older than 3 days.
> Agree that we need a longer term solution.
>
> Passing recent tests on all executors except jenkins-12, which has not
> scheduled recent builds for the past 13 days. Not scheduling:
> https://builds.apache.org/computer/apache-beam-jenkins-12/builds
> <https://www.google.com/url?q=https://builds.apache.org/computer/apache-beam-jenkins-12/builds&sa=D>
> Recent passing builds:
> https://builds.apache.org/computer/apache-beam-jenkins-1/builds
> <https://www.google.com/url?q=https://builds.apache.org/computer/apache-beam-jenkins-1/builds&sa=D>
> https://builds.apache.org/computer/apache-beam-jenkins-2/builds
> <https://www.google.com/url?q=https://builds.apache.org/computer/apache-beam-jenkins-2/builds&sa=D>
> https://builds.apache.org/computer/apache-beam-jenkins-3/builds
> <https://www.google.com/url?q=https://builds.apache.org/computer/apache-beam-jenkins-3/builds&sa=D>
> https://builds.apache.org/computer/apache-beam-jenkins-4/builds
> <https://www.google.com/url?q=https://builds.apache.org/computer/apache-beam-jenkins-4/builds&sa=D>
> https://builds.apache.org/computer/apache-beam-jenkins-5/builds
> <https://www.google.com/url?q=https://builds.apache.org/computer/apache-beam-jenkins-5/builds&sa=D>
> https://builds.apache.org/computer/apache-beam-jenkins-6/builds
> <https://www.google.com/url?q=https://builds.apache.org/computer/apache-beam-jenkins-6/builds&sa=D>
> https://builds.apache.org/computer/apache-beam-jenkins-7/builds
> <https://www.google.com/url?q=https://builds.apache.org/computer/apache-beam-jenkins-7/builds&sa=D>
> https://builds.apache.org/computer/apache-beam-jenkins-8/builds
> <https://www.google.com/url?q=https://builds.apache.org/computer/apache-beam-jenkins-8/builds&sa=D>
> https://builds.apache.org/computer/apache-beam-jenkins-9/builds
> <https://www.google.com/url?q=https://builds.apache.org/computer/apache-beam-jenkins-9/builds&sa=D>
> https://builds.apache.org/computer/apache-beam-jenkins-10/builds
> <https://www.google.com/url?q=https://builds.apache.org/computer/apache-beam-jenkins-10/builds&sa=D>
> https://builds.apache.org/computer/apache-beam-jenkins-11/builds
> <https://www.google.com/url?q=https://builds.apache.org/computer/apache-beam-jenkins-11/builds&sa=D>
> https://builds.apache.org/computer/apache-beam-jenkins-13/builds
> <https://www.google.com/url?q=https://builds.apache.org/computer/apache-beam-jenkins-13/builds&sa=D>
> https://builds.apache.org/computer/apache-beam-jenkins-14/builds
> <https://www.google.com/url?q=https://builds.apache.org/computer/apache-beam-jenkins-14/builds&sa=D>
> https://builds.apache.org/computer/apache-beam-jenkins-15/builds
> <https://www.google.com/url?q=https://builds.apache.org/computer/apache-beam-jenkins-15/builds&sa=D>
> https://builds.apache.org/computer/apache-beam-jenkins-16/builds
> <https://www.google.com/url?q=https://builds.apache.org/computer/apache-beam-jenkins-16/builds&sa=D>
>
> On Fri, Mar 6, 2020 at 11:54 AM Ahmet Altay <[email protected]> wrote:
>
>> +Alan Myrvold <[email protected]> is doing a one time cleanup. I agree
>> that we need to have a solution to automate this task or address the root
>> cause of the buildup.
>>
>> On Thu, Mar 5, 2020 at 2:47 AM Michał Walenia <[email protected]>
>> wrote:
>>
>>> Hi there,
>>> it seems we have a problem with Jenkins workers again. Nodes 1 and 7
>>> both fail jobs with "No space left on device".
>>> Who is the best person to contact in these cases (someone with access
>>> permissions to the workers).
>>>
>>> I also noticed that such errors are becoming more and more frequent
>>> recently and I'd like to discuss how can this be remedied. Can a cleanup
>>> task be automated on Jenkins somehow?
>>>
>>> Regards
>>> Michal
>>>
>>> --
>>>
>>> Michał Walenia
>>> Polidea <https://www.polidea.com/> | Software Engineer
>>>
>>> M: +48 791 432 002 <+48791432002>
>>> E: [email protected]
>>>
>>> Unique Tech
>>> Check out our projects! <https://www.polidea.com/our-work>
>>>
>>

Reply via email to