Re: [PATCH 0/4] submodule: parallelize status

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 23, 2022, 22:56 UTC
Message-ID: <xmqqleq9snr8.fsf@gitster.g>
In-Reply-To: <20220922232947.631309-1-calvinwan@google.com>

Calvin Wan <calvinwan@google.com> writes:

> Future work: The reason why status is much slower on a cold cache vs
> warm cache is mainly due to refreshing the index. It is worth
> investigating whether this is entirely necessary.

I suspect that the CI breakage

  https://github.com/git/git/actions/runs/3115673002/jobs/5052804463

is due to this topic.

In "SANTIZE=leak GIT_TEST_PASSING_SANITIZE_LEAK=true make test" run locally, I see t7507 failing quite badly.

$ 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.