From: larsxschneider@gmail.com
To: git@vger.kernel.org
Cc: sunshine@sunshineco.com, sschuberth@gmail.com,
Matthieu.Moy@grenoble-inp.fr, avila.jn@gmail.com,
luke@diamand.org, dturner@twopensource.com,
Lars Schneider <larsxschneider@gmail.com>
Subject: [PATCH v4 3/4] git-p4: retry kill/cleanup operations in tests with timeout
Date: Fri, 6 Nov 2015 09:58:42 +0100 [thread overview]
Message-ID: <1446800323-2914-4-git-send-email-larsxschneider@gmail.com> (raw)
In-Reply-To: <1446800323-2914-1-git-send-email-larsxschneider@gmail.com>
From: Lars Schneider <larsxschneider@gmail.com>
In rare cases kill/cleanup operations in tests fail. Retry these
operations with a timeout to make the test less flaky.
Signed-off-by: Lars Schneider <larsxschneider@gmail.com>
---
t/lib-git-p4.sh | 31 +++++++++++++++++++++++--------
1 file changed, 23 insertions(+), 8 deletions(-)
diff --git a/t/lib-git-p4.sh b/t/lib-git-p4.sh
index b1660f6..9043b51 100644
--- a/t/lib-git-p4.sh
+++ b/t/lib-git-p4.sh
@@ -10,6 +10,10 @@ TEST_NO_CREATE_REPO=NoThanks
# the defined timeout in seconds.
P4D_TIMEOUT=300
+# Some operations require multiple attempts to be successful. Define
+# here the maximal retry timeout in seconds.
+RETRY_TIMEOUT=60
+
. ./test-lib.sh
if ! test_have_prereq PYTHON
@@ -138,14 +142,24 @@ p4_add_user() {
EOF
}
+retry_until_success() {
+ timeout=$(($(date +%s) + $RETRY_TIMEOUT))
+ until "$@" 2>/dev/null || test $(date +%s) -gt $timeout
+ do :
+ done
+}
+
+retry_until_fail() {
+ timeout=$(($(date +%s) + $RETRY_TIMEOUT))
+ until ! "$@" 2>/dev/null || test $(date +%s) -gt $timeout
+ do :
+ done
+}
+
kill_p4d() {
pid=$(cat "$pidfile")
- # it had better exist for the first kill
- kill $pid &&
- for i in 1 2 3 4 5 ; do
- kill $pid >/dev/null 2>&1 || break
- sleep 1
- done &&
+ retry_until_fail kill $pid
+ retry_until_fail kill -9 $pid
# complain if it would not die
test_must_fail kill $pid >/dev/null 2>&1 &&
rm -rf "$db" "$cli" "$pidfile" &&
@@ -153,8 +167,9 @@ kill_p4d() {
}
cleanup_git() {
- rm -rf "$git" &&
- mkdir "$git"
+ retry_until_success rm -r "$git"
+ test_must_fail test -d "$git" &&
+ retry_until_success mkdir "$git"
}
marshal_dump() {
--
2.5.1
next prev parent reply other threads:[~2015-11-06 8:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 8:58 [PATCH v4 0/4] Add Travis CI support larsxschneider
2015-11-06 8:58 ` [PATCH v4 1/4] add function test_must_fail_or_sigpipe and use it to fix flaky tests larsxschneider
2015-11-06 18:27 ` Junio C Hamano
2015-11-06 18:49 ` Junio C Hamano
2015-11-06 8:58 ` [PATCH v4 2/4] git-p4: add p4d timeout in tests larsxschneider
2015-11-06 9:23 ` Eric Sunshine
2015-11-06 13:20 ` Lars Schneider
2015-11-06 8:58 ` larsxschneider [this message]
2015-11-06 9:28 ` [PATCH v4 3/4] git-p4: retry kill/cleanup operations in tests with timeout Eric Sunshine
2015-11-06 9:47 ` Lars Schneider
2015-11-06 13:19 ` Lars Schneider
2015-11-06 8:58 ` [PATCH v4 4/4] Add Travis CI support larsxschneider
2015-11-06 9:56 ` Eric Sunshine
2015-11-06 13:18 ` Lars Schneider
[not found] ` <22B2C2B1-9260-4EC0-A4C5-C7F7DDD388BA@gmail.com>
2015-11-06 13:20 ` Sebastian Schuberth
2015-11-06 13:28 ` Lars Schneider
2015-11-06 13:36 ` Sebastian Schuberth
2015-11-06 13:55 ` Lars Schneider
2015-11-06 13:57 ` Sebastian Schuberth
2015-11-06 14:08 ` Lars Schneider
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1446800323-2914-4-git-send-email-larsxschneider@gmail.com \
--to=larsxschneider@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=avila.jn@gmail.com \
--cc=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=luke@diamand.org \
--cc=sschuberth@gmail.com \
--cc=sunshine@sunshineco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).