git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v5 3/6] git-p4: retry kill/cleanup operations in tests with timeout

From
Luke Diamand <luke@diamand.org>
Date
Nov 16, 2015, 08:36 UTC
Message-ID
<5649958F.2010407@diamand.org>
In-Reply-To
<1447592920-89228-4-git-send-email-larsxschneider@gmail.com>
On 15/11/15 13:08, larsxschneider@gmail.com wrote:
> 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.

Should there be a sleep in that retry_until_success loop so that it doesn't spin sending signals to p4d?

Do we need to worry about the time offset being updated (e.g. NTP) while this is running?

Show 29 quoted lines
>
> 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 7548225..8d6b48f 100644
> --- a/t/lib-git-p4.sh
> +++ b/t/lib-git-p4.sh
> @@ -6,6 +6,10 @@
>   # a subdirectory called "$git"
>   TEST_NO_CREATE_REPO=NoThanks
>
> +# 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
> @@ -121,22 +125,33 @@ p4_add_user() {
>   	EOF
>   }
>
> +retry_until_success() {
> +    timeout=$(($(date +%s) + $RETRY_TIMEOUT))
> +    until "$@" 2>/dev/null || test $(date +%s) -gt $timeout
> +    do :
  sleep here?
Show 7 quoted lines
> +    done
> +}
> +
> +retry_until_fail() {
> +    timeout=$(($(date +%s) + $RETRY_TIMEOUT))
> +    until ! "$@" 2>/dev/null || test $(date +%s) -gt $timeout
> +    do :
  sleep here?
Show 28 quoted lines
> +    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"
>   }
>
>   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() {
>
Previous: larsxschneider@gmail.comNext: Lars Schneider
Message 5 of 19 in “Add Travis CI support”
  1. 0/6 Add Travis CI supportlarsxschneider@gmail.com, Nov 15, 2015
  2. 1/6 implement test_might_fail using a refactored test_must_faillarsxschneider@gmail.com, Nov 15, 2015
  3. 2/6 add "ok=sigpipe" to test_must_fail and use it to fix flaky testslarsxschneider@gmail.com, Nov 15, 2015
  4. 3/6 git-p4: retry kill/cleanup operations in tests with timeoutlarsxschneider@gmail.com, Nov 15, 2015
  5. Luke DiamandNov 16, 2015
  6. Lars SchneiderNov 17, 2015
  7. Luke DiamandNov 17, 2015
  8. Eric SunshineNov 16, 2015
  9. Lars SchneiderNov 17, 2015
  10. Eric SunshineNov 17, 2015
  11. Luke DiamandNov 17, 2015
  12. Eric SunshineNov 17, 2015
  13. Luke DiamandNov 17, 2015
  14. 4/6 git-p4: add p4d timeout in testslarsxschneider@gmail.com, Nov 15, 2015
  15. Luke DiamandNov 16, 2015
  16. 5/6 git-p4: add trap to kill p4d on test exitlarsxschneider@gmail.com, Nov 15, 2015
  17. Luke DiamandNov 16, 2015
  18. Lars SchneiderNov 17, 2015
  19. 6/6 Add Travis CI supportlarsxschneider@gmail.com, Nov 15, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.