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
Eric Sunshine <sunshine@sunshineco.com>
Date
Nov 17, 2015, 08:35 UTC
Message-ID
<CAPig+cR8igO1bWNgma_yZqrcru_jnKchpRH+i2_AaNj8Atcb9g@mail.gmail.com>
In-Reply-To
<52A9F66D-12C4-4BB5-A2D4-C476A1E12DC5@gmail.com>

On Tue, Nov 17, 2015 at 3:28 AM, Lars Schneider <larsxschneider@gmail.com> wrote:

Show 30 quoted lines
> On 16 Nov 2015, at 22:14, Eric Sunshine <sunshine@sunshineco.com> wrote:
>> On Sun, Nov 15, 2015 at 8:08 AM,  <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.
>>>
>>> Signed-off-by: Lars Schneider <larsxschneider@gmail.com>
>>> ---
>>> diff --git a/t/lib-git-p4.sh b/t/lib-git-p4.sh
>>> @@ -121,22 +125,33 @@ p4_add_user() {
>>>        EOF
>>> }
>>>
>>> +retry_until_success() {
>>> +    timeout=$(($(date +%s) + $RETRY_TIMEOUT))
>>
>> There was some discussion previously[1] about detecting dynamically
>> whether 'date +%s' was supported. Was this something that you intended
>> to do, or did you decide against it since p4 is not supported on such
>> platforms?
>>
>> Same question also applies to patch 4/6.
>
> While implementing it I thought more about it. P4D is only
> supported on platforms that support the date function. That means
> these tests will only run on platforms that support the date
> function. Consequently I wondered if this would justify the
> slightly more complicated code. However, if you think this change
> would help the patch to get accepted then I will add it.

I don't feel strongly about it, and it's not my call anyhow. Opinions of Junio, Peff (as interim maintainer), and Luke weigh much more heavily than my own. Punting on dynamic detection of "date +%s" may be perfectly acceptable with the attitude that it can be implemented later if someone runs across a case where it's actually needed.

Previous: Lars SchneiderNext: Luke Diamand
Message 10 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.