summaryrefslogtreecommitdiff
path: root/morphlib/plugins/gc_plugin.py
Commit message (Collapse)AuthorAgeFilesLines
* Stop moving staging areas of failed buildsTiago Gomes2015-09-011-1/+27
| | | | | | | | | | | | | | | | | | | | | Stop moving staging areas of failed builds from the 'staging' directory to the 'failed' directory. Moving staging areas make it very difficult to debug build failures on the build essential chunks, as the paths set on the configure scripts and some environment variables (e.g. STAGE2_SYSROOT, DESTDIR) will be invalid after moving the staging area. This change will also make it easier to create scripts that chroot n environment similiar to the one where the build failure occurred. To make it still possible to safely do a build an run `morph gc` in parallel, we use flock(2) to control access to the staging area directory. Also, move the `test_supports_non_isolated_mode` test into a different class, as it requires a different SetUp() routine (the staging area is contructed with different parameters). Change-Id: I06c3c435ad05c12afabc0adc2a9d4f8a284ccc02
* Use the modern way of the GPL copyright header: URL instead real addressJavier Jardón2015-03-161-3/+2
| | | | Change-Id: I992dc0c1d40f563ade56a833162d409b02be90a0
* Don't delete subdirectories of tempdir in gc pluginSam Thursfield2014-06-131-0/+3
| | | | | | There is code that assumes these exist in at least one place: StagingArea.abort(). That code should be fixed, but we should also stop deleting them every time we run 'morph gc'.
* Make morph gc clear out deployments in tmpdirPaul Sherwood2014-06-071-1/+6
| | | | | | | | Generally deployment temp dirs are removed by morph during deployment, but in some cases deployment dirs may not be cleared up, for example if morph gets a SIGKILL or something unexpected happens that causes morph to terminate without having a chance to cleanup.
* Update Copyright and wrap lines longer than 79 charsPedro Alvarez2014-02-041-2/+3
|
* Improve help for gc commandrichardipsum/gc_plugin_improve_helpRichard Ipsum2014-01-301-6/+9
|
* LocalArtifactCache now takes a an FS objectDaniel Firth2013-12-201-1/+2
|
* Only attempt to clean up artifactsRichard Maw2013-06-111-1/+2
| | | | | | | | | | | | Because the whole cachedir was considered, and not just the artifacts tree, it would recursively consider every file an artifact, incuding cached gits and ccache. This made it slower and remove things before they were due, since only the artifact cache is guaranteed to set mtimes on access. This wouldn't cause incorrect builds, since any cached objects get re-generated, but it was definitely not desired behaviour.
* GC Plugin: Fix usage of satus.Richard Maw2013-06-091-1/+1
| | | | I don't know how that one slipped through.
* plugins: add morph gc subcommandRichard Maw2013-06-071-0/+158
This removes staging areas and extracted chunks from --tempdir. Then asks the local artifact cache what artifacts it has and how old they are, removing all sources older than --cachedir-artifact-delete-older-than, and may delete other sources that are younger than --cachedir-artifact-keep-younger-than if it still needs to make space.