From: Taylor Blau <me@ttaylorr.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Mark Hills <mark@xwax.org>,
git@vger.kernel.org, Matheus Tavares <matheus.bernardino@usp.br>
Subject: Re: Consist timestamps within a checkout/clone
Date: Mon, 31 Oct 2022 16:36:53 -0400 [thread overview]
Message-ID: <Y2Ax5XOgSOOcgo8J@nand.local> (raw)
In-Reply-To: <221031.86zgdb68p3.gmgdl@evledraar.gmail.com>
On Mon, Oct 31, 2022 at 09:21:20PM +0100, Ævar Arnfjörð Bjarmason wrote:
> I think you're almost certainly running into the parallel checkout,
> which is new in that revision range. Try tweaking checkout.workers and
> checkout.thresholdForParallelism (see "man git-config").
>
> I can't say without looking at the code/Makefile (and even then, I don't
> have time to dig here:), but if I had to bet I'd say that your
> dependencies have probably always been broken with these checked-in
> files, but they happend to work out if they were checked out in sorted
> order.
>
> And now with the parallel checkout they're not guaranteed to do that, as
> some workers will "race ahead" and finish in an unpredictable order.
Doesn't checkout.thresholdForParallelism only matter when
checkout.workers != 1?
So what you wrote seems like a reasonable explanation, but only if the
original reporter set checkout.workers to imply the non-sequential
behavior in the first place.
That said...
- I also don't know off-hand of a place where we've defined the order
where Git will checkout files in the working copy. So depending on
that behavior isn't a safe thing to do.
- Committing build artifacts into your repository is generally
discouraged.
So while I'd guess that setting `checkout.workers` back to "1" (if it
wasn't already) will probably restore the existing behavior, counting
on that behavior in the first place is wrong.
Thanks,
Taylor
next prev parent reply other threads:[~2022-10-31 20:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 19:01 Consist timestamps within a checkout/clone Mark Hills
2022-10-31 20:17 ` Andreas Schwab
2022-10-31 20:21 ` Ævar Arnfjörð Bjarmason
2022-10-31 20:36 ` Taylor Blau [this message]
2022-10-31 22:31 ` Mark Hills
2022-10-31 22:42 ` rsbecker
2022-11-01 18:34 ` Ævar Arnfjörð Bjarmason
2022-10-31 22:29 ` Mark Hills
2022-11-01 17:46 ` Ævar Arnfjörð Bjarmason
2022-11-02 14:16 ` Matheus Tavares
2022-11-02 14:28 ` Matheus Tavares
2022-11-01 13:55 ` Marc Branchaud
2022-11-02 14:45 ` Ævar Arnfjörð Bjarmason
2022-11-03 13:46 ` Marc Branchaud
2022-11-01 14:34 ` Erik Cervin Edin
2022-11-01 15:53 ` Ævar Arnfjörð Bjarmason
2022-11-03 13:02 ` Erik Cervin Edin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y2Ax5XOgSOOcgo8J@nand.local \
--to=me@ttaylorr.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=mark@xwax.org \
--cc=matheus.bernardino@usp.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).