[<prev] [next>] [day] [month] [year] [list]
Message-ID: <161313344671.23325.11260337432529418228.tip-bot2@tip-bot2>
Date: Fri, 12 Feb 2021 12:37:26 -0000
From: "tip-bot2 for Paul E. McKenney" <tip-bot2@...utronix.de>
To: linux-tip-commits@...r.kernel.org
Cc: "Paul E. McKenney" <paulmck@...nel.org>, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: [tip: core/rcu] torture: Make kvm.sh return failure upon build failure
The following commit has been merged into the core/rcu branch of tip:
Commit-ID: 23239fc075d60a942101227c42353b5ced804269
Gitweb: https://git.kernel.org/tip/23239fc075d60a942101227c42353b5ced804269
Author: Paul E. McKenney <paulmck@...nel.org>
AuthorDate: Mon, 23 Nov 2020 10:41:57 -08:00
Committer: Paul E. McKenney <paulmck@...nel.org>
CommitterDate: Mon, 04 Jan 2021 14:01:22 -08:00
torture: Make kvm.sh return failure upon build failure
The kvm.sh script uses kvm-find-errors.sh to evaluate whether or not
a build failed. Unfortunately, kvm-find-errors.sh returns success if
there are no failed runs (including when there are no runs at all) even if
there are build failures. This commit therefore makes kvm-find-errors.sh
return failure in response to build failures.
Signed-off-by: Paul E. McKenney <paulmck@...nel.org>
---
tools/testing/selftests/rcutorture/bin/kvm-find-errors.sh | 8 ++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/rcutorture/bin/kvm-find-errors.sh b/tools/testing/selftests/rcutorture/bin/kvm-find-errors.sh
index 6f50722..be26598 100755
--- a/tools/testing/selftests/rcutorture/bin/kvm-find-errors.sh
+++ b/tools/testing/selftests/rcutorture/bin/kvm-find-errors.sh
@@ -39,6 +39,7 @@ done
if test -n "$files"
then
$editor $files
+ editorret=1
else
echo No build errors.
fi
@@ -62,5 +63,10 @@ then
exit 1
else
echo No errors in console logs.
- exit 0
+ if test -n "$editorret"
+ then
+ exit $editorret
+ else
+ exit 0
+ fi
fi
Powered by blists - more mailing lists