diff options
| author | Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org> | 2018-12-05 15:27:33 +0000 |
|---|---|---|
| committer | Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org> | 2018-12-07 12:32:34 +0000 |
| commit | 5c0fc7c61549794d5e5ee861dc9bea60fadb73d4 (patch) | |
| tree | 8219e2263fe699f6ff5fd32526bd9b96b7376ae9 /tcwg_kernel-bisect.sh | |
| parent | 828a6b5812b9a00a9612333e50096fe1932ac139 (diff) | |
tcwg_kernel-bisect.sh: Make sure artifacts contain "bad" logs
We already reproduce "bad" build when --confirm_failure is true,
and this change makes it easy to generate "bad" logs when running
manually. E.g., with a command like
~/jenkins-scripts/tcwg_kernel-bisect.sh --toolchain gnu \
--current_project gcc --target aarch64 \
--bad_rev 57e4ba18100241b927a99283f8cfbcc5b76793c2 \
--baseline_rev 57e4ba18100241b927a99283f8cfbcc5b76793c2^
we will now get both "good" and "bad" logs.
Change-Id: I2bdff1bd9a91331fa25089f3e44a703c1cd9990e
Diffstat (limited to 'tcwg_kernel-bisect.sh')
| -rwxr-xr-x | tcwg_kernel-bisect.sh | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/tcwg_kernel-bisect.sh b/tcwg_kernel-bisect.sh index a70d7727..c96da898 100755 --- a/tcwg_kernel-bisect.sh +++ b/tcwg_kernel-bisect.sh @@ -161,6 +161,19 @@ if [ x"$merge_base" != x"$good_rev" -a x"$origin" = x"linux-next.git" ]; then fi fi +if ! $confirm_failure; then + git checkout --detach $bad_rev + ../bisect-run.sh & + res=0 && wait $! || res=$? + + if [ x"$res" = x"0" ]; then + echo "ERROR: build for bad_rev $bad_rev succeeded" + exit 1 + fi + + mv "$artifacts/build-$bad_rev" "$artifacts/build-$bad_rev-bad" +fi + git bisect start $bad_rev $good_rev 2>&1 | tee $artifacts/bisect.log # "git bisect run" can fail (exit with non-zero) in a number of cases: |