On Tue, Nov 12, 2013 at 10:41:02AM +0100, Hugo Trippaers wrote: > Heya, > > The builds were stuck because the system ran out of diskspace. > Cleaned some of the unused job folders to get some space back. >
This happened once again on master. All master jobs had been moved out to other build machines. Some old jobs had their workspaces still left around which I got rid of just now: bash-4.2$ ls -1 | xargs -n1 du -sh 442M build-4.1 399M build-docs-admin-4.0 921M build-docs-admin-master 148M build-docs-devguide-master 156M build-docs-install-master 718M build-docs-master 505M build-docs-midonet-master 505M build-docs-niciranvp-master 423M build-docs-release-notes-4.0 148M build-docs-release-notes-master 473M build-test-archive 761M docs-4.1-adminguide 624M docs-4.1-installguide 501M docs-4.1-plugin-nicira-nvp 494M docs-4.1-releasenotes 478M docs-4.3-clients-wrappers-guide 457M docs-4.3-gsoc-guide 399M docs-master 4.0K dot-git-README 4.0K jobs-README 4.0K mgmt-build-reviewboard-requests 753M test-integration-archive 380M verify-license-4.0 In the haste to get 4.2.1 results out I erased the job history accidentally. Shouldn't have messed with the jenkins machine directly. Apologize for that! I plan to work on moving all infra to remotely config managed. Any and every help welcome in this regard! > > Cheers, > > Hugo -- Prasanna., ------------------------ Powered by BigRock.com
