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

Re: Parallel fetch and commit graph writing results in locking failure (even on linux)

From
Jeff King <peff@peff.net>
Date
Dec 13, 2019, 19:52 UTC
Message-ID
<20191213195215.GA862734@coredump.intra.peff.net>
In-Reply-To
<bdb9201f-b77f-ab3c-251f-d902c76fa9bc@gmail.com>
On Fri, Dec 13, 2019 at 02:35:47PM -0500, Derrick Stolee wrote:
Show 8 quoted lines
> I don't think so. I think you just found a bug where the
> fetch.writeCommitGraph logic doesn't work with parallel fetch
> jobs (only one can write at a time).
> 
> I believe the fix would be to write the commit-graph after
> all of the jobs have completed, which should mean we need to
> move the call to write_commit_graph_reachable() somewhere else
> inside builtin/fetch.c.

This should be fixed in master by bcb06e204c (Merge branch 'js/fetch-multi-lockfix', 2019-12-01), I think.

-Peff
Previous: Derrick StoleeNext: Derrick Stolee
Message 3 of 8 in “Parallel fetch and commit graph writing results in locking failure (even on linux)”
  1. Thomas BraunDec 13, 2019
  2. Derrick StoleeDec 13, 2019
  3. Jeff KingDec 13, 2019
  4. Derrick StoleeDec 13, 2019
  5. SZEDER GáborDec 13, 2019
  6. Thomas BraunDec 15, 2019
  7. german language fix: Generierung vs. Generation [was: Re: Parallel fetch and commit graph writing results in locking failure (even on linux)]Thomas Braun, Dec 15, 2019
  8. l10n: de.po: Reword generation numbersRalf Thielow, Dec 15, 2019

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.