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

Re: [PATCH] read-cache: report lock error when refreshing index

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 1, 2025, 19:21 UTC
Message-ID
<xmqqv7obk98v.fsf@gitster.g>
In-Reply-To
<t4czubzmfuihxzmefwwhcel5qyss35gmodhfhvkfyiwitb5osw@d33acdbtds63>
Justin Tobler <jltobler@gmail.com> writes:
Show 8 quoted lines
>>  		test_must_fail git stash create 2>err &&
>> -		test_cmp expect err
>> +		test_grep "error: Unable to create '.*index.lock'" err
>
> The test now checks for the explicit lock error message. The check for
> the "error: could not write index" message is also removed even though
> it should still be present in the output. Should we also continue to
> grep for that message too?

Probably. I was wondering which part of the patch removed the existing message while reading this update to the test.

Thanks.
Previous: Justin ToblerNext: Han Young
Message 3 of 6 in “read-cache: report lock error when refreshing index”
  1. read-cache: report lock error when refreshing indexHan Young, Jul 1, 2025
  2. Justin ToblerJul 1, 2025
  3. Junio C HamanoJul 1, 2025
  4. read-cache: report lock error when refreshing indexHan Young, Jul 3, 2025
  5. Junio C HamanoJul 7, 2025
  6. Han YoungJul 8, 2025

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.