From 0b630c5a841951d209e305eab8837729fd5332da Mon Sep 17 00:00:00 2001 From: Maxim Kuvyrkov Date: Sat, 19 Jan 2019 14:52:26 +0000 Subject: tcwg_kernel-bisect.sh: Put bisect test script into artifacts/ The bisect script will be used in updated instructions to reproduce the build. Change-Id: I67b16e4f86f55b80dea39980028b244a95e2417b --- tcwg_kernel-bisect.sh | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/tcwg_kernel-bisect.sh b/tcwg_kernel-bisect.sh index 8050e596..e9d42f5b 100755 --- a/tcwg_kernel-bisect.sh +++ b/tcwg_kernel-bisect.sh @@ -94,7 +94,7 @@ EOF # for $bad_rev (result metric <1000 in the above scenario), so we would # skip revisions between rev_20 and rev_22. This might cause other edge # cases to be handled sub-optimally, though. -cat > ../bisect-run.sh < $artifacts/test.sh <&1 | tee $artifacts/bisect.log # - something else? # In all these cases we want to reset baseline to HEAD, so that we catch # most of the commits that introduced change in the result metric. -git bisect run ../bisect-run.sh 2>&1 | tee -a $artifacts/bisect.log & +git bisect run $artifacts/test.sh 2>&1 | tee -a $artifacts/bisect.log & res=0 && wait $! || res=$? if [ x"$res" = x"0" ]; then @@ -270,7 +270,7 @@ if [ -f $artifacts/first-bad ]; then cd $current_project echo "Testing last_good $last_good (hoping for success)" git checkout --detach "$last_good" - ../bisect-run.sh & + $artifacts/test.sh & res=0 && wait $! || res=$? if [ x"$res" != x"0" ]; then # It seems $last_good was on a path that tested good, even though -- cgit v1.2.3