I minimized the storage size required for the Fuel development builds because they kept erroring out with the message "pharo-vm/PharoV40.sources: write error (disk full?). Continue? (y/n/^C) â Now that Iâve freed up some space the builds work again, the question is for how long. Is the space that low on the CI? Cheers, Max
Le 4 mars 2016 à 16:25, Max Leske a écrit :
I minimized the storage size required for the Fuel development builds because they kept erroring out with the message
"pharo-vm/PharoV40.sources: write error (disk full?). Continue? (y/n/^C) â
Now that Iâve freed up some space the builds work again, the question is for how long. Is the space that low on the CI?
where? on a slave? some slaves can become full because they keep a lot of different workspaces for different jobs, and at the end, they use a lot of space.
On 04 Mar 2016, at 16:36, Christophe Demarey <christophe.demarey@inria.fr> wrote:
Le 4 mars 2016 à 16:25, Max Leske a écrit :
I minimized the storage size required for the Fuel development builds because they kept erroring out with the message
"pharo-vm/PharoV40.sources: write error (disk full?). Continue? (y/n/^C) â
Now that Iâve freed up some space the builds work again, the question is for how long. Is the space that low on the CI?
where? on a slave? some slaves can become full because they keep a lot of different workspaces for different jobs, and at the end, they use a lot of space.
The one Iâve seen (there might have been others) was https://ci.inria.fr/pharo-contribution/computer/pharo-contribution-linux64-3
Max Leske <maxleske@gmail.com> writes:
The one Iâve seen (there might have been others) was https://ci.inria.fr/pharo-contribution/computer/pharo-contribution-linux64-3
I had a problem on the same slave (94% disk full). I deleted /builds. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
participants (3)
-
Christophe Demarey -
Damien Cassou -
Max Leske