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

Re: Build: support - Fix to avoid high memory footprint

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jul 24, 2024, 08:26 UTC
Message-ID
<7cef2d49-2794-47d8-ca56-8118410aeb48@gmx.de>
In-Reply-To
<194BFBB9-FCF0-43F7-BFC2-B055351B5376@ibm.com>
Hi Haritha,
On Wed, 24 Jul 2024, Haritha D wrote:
> I have raised https://github.com/git/git/pull/1744. The win test(5) test
> case failed stating the reason as "The Operation cancelled". I saw that
> it failed after 5 hours 59 minutes of running the test cases(build). How
> do I handle this?

It would seem that the rate of random timeouts and general flakiness of Git's test suite has increased as of late.

I started a re-run of the timed-out job: https://github.com/git/git/actions/runs/10043066326/job/27846613495?pr=1744

Ciao, Johannes

Previous: Haritha D
Message 2 of 2 in “Build: support - Fix to avoid high memory footprint”
  1. Haritha DJul 24, 2024
  2. Johannes SchindelinJul 24, 2024

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.