diff options
author | Simon Glass <sjg@chromium.org> | 2015-02-05 22:06:13 -0700 |
---|---|---|
committer | Simon Glass <sjg@chromium.org> | 2015-04-18 16:24:24 -0600 |
commit | 88c8dcf94945937bea94b330067fe68fe24665b2 (patch) | |
tree | 8a5d8b82ed872c9d1ade9d9c13a7b17f6c82283d /tools/gpimage-common.c | |
parent | 40f11fce7c686f2b51ae109c4085fb5988c5631c (diff) | |
download | u-boot-imx-88c8dcf94945937bea94b330067fe68fe24665b2.zip u-boot-imx-88c8dcf94945937bea94b330067fe68fe24665b2.tar.gz u-boot-imx-88c8dcf94945937bea94b330067fe68fe24665b2.tar.bz2 |
buildman: Adjust the 'aborted' heuristic for writing output
At present buildman tries to detect an aborted build and doesn't record a
result in that case. This is to make sure that an abort (e.g. with Ctrl-C)
does not mark the build as done. Without this option, buildman would never
retry the build unless -f/-F are provided. The effect is that aborting the
build creates 'fake errors' on whatever builds buildman happens to be
working on at the time.
Unfortunately the current test is not reliable and this detection can
trigger if a required toolchain tool is missing. In this case the toolchain
problem is never reported.
Adjust the logic to continue processing the build result, mark the build as
done (and failed), but with a return code which indicates that it should be
retried.
The correct fix is to fully and correctly detect an aborted build, quit
buildman immediately and not write any partial build results in this case.
Unfortunately this is currently beyond my powers and is left as an exercise
for the reader (and patches are welcome).
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'tools/gpimage-common.c')
0 files changed, 0 insertions, 0 deletions