summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMaxim Kuvyrkov <maxim.kuvyrkov@linaro.org>2019-01-19 14:52:26 +0000
committerMaxim Kuvyrkov <maxim.kuvyrkov@linaro.org>2019-01-22 13:38:03 +0000
commit0b630c5a841951d209e305eab8837729fd5332da (patch)
treeb1cb6eb683f98f0385a60c8f4fb831b6e4aff25d
parentdd49fbf78ef3dde178adff63cfaee8b5d824da48 (diff)
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
-rwxr-xr-xtcwg_kernel-bisect.sh14
1 files 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 <<EOF
+cat > $artifacts/test.sh <<EOF
#!/bin/sh
rev=\$(git rev-parse HEAD)
cd ..
@@ -117,7 +117,7 @@ else
exit 0
fi
EOF
-chmod +x ../bisect-run.sh
+chmod +x $artifacts/test.sh
# Workaround linux-next/master rebasing on top of linux-next/stable.
# Try to find $good_rev that is "good" compared to baseline
@@ -128,7 +128,7 @@ origin=$(basename "$origin")
if [ x"$merge_base" != x"$good_rev" -a x"$origin" = x"linux-next.git" ]; then
echo "Testing merge_base $merge_base (hoping for success)"
git checkout --detach "$merge_base"
- ../bisect-run.sh &
+ $artifacts/test.sh &
res=0 && wait $! || res=$?
if [ x"$res" != x"0" ]; then
# Check if we can use linux-next/stable as our pre-last resort.
@@ -138,7 +138,7 @@ declare -g linux_next_stable=$linux_next_stable
EOF
echo "Testing linux_next:stable $linux_next_stable (hoping for success)"
git checkout --detach $linux_next_stable
- ../bisect-run.sh &
+ $artifacts/test.sh &
res=0 && wait $! || res=$?
if [ x"$res" = x"0" ]; then
good_rev=$linux_next_stable
@@ -156,7 +156,7 @@ declare -g mainline_master=$mainline_master
EOF
echo "Testing mainline_master $mainline_master (hoping for success)"
git checkout --detach $mainline_master
- ../bisect-run.sh &
+ $artifacts/test.sh &
res=0 && wait $! || res=$?
if [ x"$res" = x"0" ]; then
good_rev=$mainline_master
@@ -201,7 +201,7 @@ git bisect start $bad_rev $good_rev 2>&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