diff options
| author | Simon Glass <sjg@chromium.org> | 2014-07-13 12:22:31 -0600 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2014-07-23 09:52:33 -0600 |
| commit | 4266dc28827454ede31cc931a3c76b67fafd31c2 (patch) | |
| tree | 54c3f78aaec052d99c13feef7b4820e3d83b51ab /tools/buildman/control.py | |
| parent | 74f96dada18edd3ebd4a1c5d39edc806a17eefcc (diff) | |
| download | u-boot-imx-4266dc28827454ede31cc931a3c76b67fafd31c2.zip u-boot-imx-4266dc28827454ede31cc931a3c76b67fafd31c2.tar.gz u-boot-imx-4266dc28827454ede31cc931a3c76b67fafd31c2.tar.bz2 | |
buildman: Add -F flag to retry failed builds
Generally a build failure with a particular commit cannot be fixed except
by changing that commit. Changing the commit will automatically cause
buildman to retry when you run it again: buildman sees that the commit
hash is different and that it has no previous build result for the new
commit hash.
However sometimes the build failure is due to a toolchain issue or some
other environment problem. In that case, retrying failed builds may yield
a different result.
Add a flag to retry failed builds. This differs from the force rebuild
flag (-f) in that it will not rebuild commits which are already marked as
succeeded.
Series-to: u-boot
Change-Id: Iac4306df499d65ff0888b1c60f06fc162a6faad8
Diffstat (limited to 'tools/buildman/control.py')
| -rw-r--r-- | tools/buildman/control.py | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tools/buildman/control.py b/tools/buildman/control.py index d2f4102..cfad535 100644 --- a/tools/buildman/control.py +++ b/tools/buildman/control.py @@ -156,6 +156,7 @@ def DoBuildman(options, args): ShowActions(series, why_selected, selected, builder, options) else: builder.force_build = options.force_build + builder.force_build_failures = options.force_build_failures # Work out which boards to build board_selected = boards.GetSelectedDict() |