72bd52e061
If the system ran out of space, or was rebooted unexpectedly, the state
of the queue symlinks, or the results STATUS files may be inconsistent.
This checks them and:
* Removes broken symlinks from queue/new and queue/run
* Removes symlinks from run and sets the build to FAILED
* Sets builds w/o a STATUS to FAILED
* Sets builds with STATUS of RUNNING to FAILED
* Creates missing queue/new symlinks to results with STATUS of WAITING
So, any builds that were running during the reboot will be FAILED, and
any that were waiting to be started will be started upon rebooting.
Resolves: rhbz#1657054
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| blueprints | ||
| repos | ||
| results | ||
| source | ||
| test_buildstamp.py | ||
| test_compose.py | ||
| test_crossdomain.py | ||
| test_projects.py | ||
| test_queue.py | ||
| test_recipes.py | ||
| test_server.py | ||
| test_timestamp.py | ||
| test_workspace.py | ||
| test_yumbase.py | ||