Hi,
I’m getting this things in logs: Downloading PharoV20.sources: http://files.pharo.org/sources//PharoV20.sources.zip pharo-vm/PharoV20.sources: write error (disk full?). Continue? (y/n/^C) warning: pharo-vm/PharoV20.sources is probably truncated did we run out of space on pharo-contribution? Uko
|
Probably and this is why we should trim our builds a bit.
> > I’m getting this things in logs: > > Downloading PharoV20.sources: > http://files.pharo.org/sources//PharoV20.sources.zip > pharo-vm/PharoV20.sources: write error (disk full?). Continue? (y/n/^C) > warning: pharo-vm/PharoV20.sources is probably truncated > > > did we run out of space on pharo-contribution? > > Uko |
you can remove my job a book I named Pharo Universe , I no longer need it, although it only contains the translated sound chapter which Stef has already copied to the other book. If I remember correctly it was inside Pharo-Contribution. On Mon, Jan 19, 2015 at 11:03 PM, stepharo <[hidden email]> wrote: Probably and this is why we should trim our builds a bit. |
yes sound is now in PharoReadyForReviews
Stef Le 19/1/15 22:24, kilon alios a écrit :
|
In reply to this post by kilon.alios
kilon alios writes: > you can remove my job a book I named Pharo Universe , I no longer need it, > although it only contains the translated sound chapter which Stef has > already copied to the other book. If I remember correctly it was inside > Pharo-Contribution. done. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill |
thanks Damien :) On Tue, Jan 20, 2015 at 7:58 AM, Damien Cassou <[hidden email]> wrote:
|
Ok, I’ve reconfigured my jobs to keep less builds and delete workspace after a build is done.
But there is still a problem with Jenkins. We have a queue of almost 600 jobs… Also there is Roassal job (while Roassal is always built on moose ci). Is this ok? Cheers. Uko
|
In reply to this post by Uko2
I've deleted a number of repeated jobs.
I wonder if it wouldn't be better to just clear the queue. Disabled VoyageMongo, as its last green build was 2014-3-14 Stephan |
In reply to this post by Uko2
The build queue is not getting smaller.
Stephan |
In reply to this post by Uko2
Who is dealing with CI? The queue is still growing and nothing seems to finish.
Stephan Jenkins tells me there are only 4 jobs using any significant amount of space: - FileTree-Pharo30-dev, - Fuel-Stable - Fuel-Development - PharoProjectCatalog2 The total is 43GB, so actually peanuts. Jobs:43 GB, Builds:43 GB, Locked builds:10 GB, Workspace:21 GB FileTree-Pharo30-dev 6 GB 6 GB 4 GB 196 MB Fuel-Stable 6 GB 6 GB 251 MB 338 MB Fuel-Development 5 GB 5 GB 363 MB 12 KB PharoProjectCatalog2 5 GB 5 GB 449 MB - Fuel-Serialize-All 1 GB 1 GB - - Versionner 710 MB 710 MB 494 MB 119 MB ... |
In reply to this post by Uko2
I've removed all jobs from the queue.
Stephan |
In reply to this post by Stephan Eggermont-3
In November 2013 the config of FileTree-Pharo30-dev was set by Camillo to keep every 10th build no matter what, and to keep every buildd for the past 30 days. And to run every day. At this point in time it seems especially excessive because no one is fixing the failing tests on Pharo 3 latest when loading FileTree from SqueakSource3. I've changed it to only keep the past 3 builds, and only build when either Pharo3 latest is updated or the FileTree repo on SqueakSource 3 is updated. It could probably be deleted entirely. |
In reply to this post by Uko2
Le 19 janv. 2015 à 11:58, Yuriy Tymchuk a écrit :
No, it looks like the fils system of a slave is full. It may happen because a slave keep the last workspace for each job that has been run on it. smime.p7s (5K) Download Attachment |
In reply to this post by Stephan Eggermont-3
Le 20 janv. 2015 à 17:35, Stephan Eggermont a écrit : > Who is dealing with CI? The queue is still growing and nothing seems to finish. I noticed that in the past. It may happen when no slave is available to execute a specific job. It happens if one or many slave go offline or if a build is stuck and no other executor is available for other jobs. I don't know if there is a good solution to manage that. My opinion is that we should just be sure that a timeout is set to every job. In addition, we could install these plugin: https://wiki.jenkins-ci.org/display/JENKINS/Purge+Build+Queue+Plugin that will ease our life if the queue grows quickly. smime.p7s (5K) Download Attachment |
In reply to this post by Paul DeBruicker
Thanks Paul.
Stef Le 21/1/15 02:36, Paul DeBruicker a écrit : > Stephan Eggermont wrote >> Who is dealing with CI? The queue is still growing and nothing seems to >> finish. >> >> Stephan >> >> Jenkins tells me there are only 4 jobs using any significant amount of >> space: >> - FileTree-Pharo30-dev, >> - Fuel-Stable >> - Fuel-Development >> - PharoProjectCatalog2 >> >> The total is 43GB, so actually peanuts. >> >> Jobs:43 GB, Builds:43 GB, Locked builds:10 GB, Workspace:21 GB >> >> FileTree-Pharo30-dev 6 GB 6 GB 4 GB 196 MB >> Fuel-Stable 6 GB 6 GB 251 MB 338 MB >> Fuel-Development 5 GB 5 GB 363 MB 12 KB >> PharoProjectCatalog2 5 GB 5 GB 449 MB - >> Fuel-Serialize-All 1 GB 1 GB - - >> Versionner 710 MB 710 MB 494 MB 119 MB >> ... > > In November 2013 the config of FileTree-Pharo30-dev was set by Camillo to > keep every 10th build no matter what, and to keep every buildd for the past > 30 days. And to run every day. > > At this point in time it seems especially excessive because no one is fixing > the failing tests on Pharo 3 latest when loading FileTree from > SqueakSource3. > > > I've changed it to only keep the past 3 builds, and only build when either > Pharo3 latest is updated or the FileTree repo on SqueakSource 3 is updated. > > It could probably be deleted entirely. > > > > -- > View this message in context: http://forum.world.st/pharo-contribution-CI-out-of-space-tp4800325p4800748.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > |
Free forum by Nabble | Edit this page |