> On 17 Apr 2018, at 06:02, monty <[hidden email]> wrote: > > https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/1820/console Yes, I know, the whole CI infrastructure is down I guess ... |
In reply to this post by monty-3
> Le 17 avr. 2018 à 06:02, monty <[hidden email]> a écrit : > > https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/1820/console > You’re right. I did some cleaning and put slaves back on line. Thanks for the report. |
Not quite fixed: https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/1822/PHARO=30,VERSION=bleedingEdge,VM=vm/console
Should we start reconfiguring jobs to keep fewer builds? > Sent: Tuesday, April 17, 2018 at 6:08 AM > From: "Christophe Demarey" <[hidden email]> > To: "Pharo Development List" <[hidden email]> > Subject: Re: [Pharo-dev] pharo-contribution CI machines out of disk space > > > > Le 17 avr. 2018 à 06:02, monty <[hidden email]> a écrit : > > > > https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/1820/console > > > > You’re right. > I did some cleaning and put slaves back on line. > > Thanks for the report. > |
Yes we should. I started to keep the minimum on mine and remove some
obsolete ones. The problem we have is that people forgot to remove their job when they do not need them anymore. Stef On Wed, Apr 18, 2018 at 5:05 AM, monty <[hidden email]> wrote: > Not quite fixed: https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/1822/PHARO=30,VERSION=bleedingEdge,VM=vm/console > > Should we start reconfiguring jobs to keep fewer builds? > >> Sent: Tuesday, April 17, 2018 at 6:08 AM >> From: "Christophe Demarey" <[hidden email]> >> To: "Pharo Development List" <[hidden email]> >> Subject: Re: [Pharo-dev] pharo-contribution CI machines out of disk space >> >> >> > Le 17 avr. 2018 à 06:02, monty <[hidden email]> a écrit : >> > >> > https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/1820/console >> > >> >> You’re right. >> I did some cleaning and put slaves back on line. >> >> Thanks for the report. >> > |
In reply to this post by monty-3
> Le 18 avr. 2018 à 05:05, monty <[hidden email]> a écrit : > > Not quite fixed: https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/1822/PHARO=30,VERSION=bleedingEdge,VM=vm/console > > Should we start reconfiguring jobs to keep fewer builds? I do not think so. The problem here is that the root partition of the slaves are full because /tmp has thousands of zip files that are downloaded by metacello from github. There is no problem with job workspace or the number of builds to keep. I will define a job running on slaves daily to remove tmp folder content. |
> Le 18 avr. 2018 à 09:52, Christophe Demarey <[hidden email]> a écrit : > > >> Le 18 avr. 2018 à 05:05, monty <[hidden email]> a écrit : >> >> Not quite fixed: https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/1822/PHARO=30,VERSION=bleedingEdge,VM=vm/console >> >> Should we start reconfiguring jobs to keep fewer builds? > > I do not think so. > The problem here is that the root partition of the slaves are full because /tmp has thousands of zip files that are downloaded by metacello from github. > There is no problem with job workspace or the number of builds to keep. > I will define a job running on slaves daily to remove tmp folder content. done: https://ci.inria.fr/pharo-contribution/job/temp-folder-cleaner/ |
Thanks. I reconfiguring mine to keep fewer anyway.
> Sent: Wednesday, April 18, 2018 at 4:02 AM > From: "Christophe Demarey" <[hidden email]> > To: "Pharo Development List" <[hidden email]> > Subject: Re: [Pharo-dev] pharo-contribution CI machines out of disk space > > > > Le 18 avr. 2018 à 09:52, Christophe Demarey <[hidden email]> a écrit : > > > > > >> Le 18 avr. 2018 à 05:05, monty <[hidden email]> a écrit : > >> > >> Not quite fixed: https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/1822/PHARO=30,VERSION=bleedingEdge,VM=vm/console > >> > >> Should we start reconfiguring jobs to keep fewer builds? > > > > I do not think so. > > The problem here is that the root partition of the slaves are full because /tmp has thousands of zip files that are downloaded by metacello from github. > > There is no problem with job workspace or the number of builds to keep. > > I will define a job running on slaves daily to remove tmp folder content. > > done: https://ci.inria.fr/pharo-contribution/job/temp-folder-cleaner/ > > > > |
Free forum by Nabble | Edit this page |