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

Re: [PATCH] t1404: increase core.packedRefsTimeout to avoid occasional test failure

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jul 31, 2018, 23:39 UTC
Message-ID
<20180731233906.GB113554@aiede.svl.corp.google.com>
In-Reply-To
<20180731233248.25482-1-szeder.dev@gmail.com>
Hi,
SZEDER Gábor wrote:
> While 3secs timeout seems plenty, and indeed is sufficient in most
> cases, on rare occasions it's just not quite enough: I saw this test
> fail in Travis CI build jobs two, maybe three times because 'git
> update-ref' timed out.

I suspect these tests will fail with valgrind (just because valgrind makes things super slow). Would it be safe to use timeout=-1?

Thanks, Jonathan

Previous: SZEDER GáborNext: SZEDER Gábor
Message 2 of 3 in “t1404: increase core.packedRefsTimeout to avoid occasional test failure”
  1. t1404: increase core.packedRefsTimeout to avoid occasional test failureSZEDER Gábor, Jul 31, 2018
  2. Jonathan NiederJul 31, 2018
  3. SZEDER GáborAug 1, 2018

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.