From: Maxime Devos <maximedevos@telenet.be>
To: zimoun <zimon.toutoune@gmail.com>, guix-devel@gnu.org
Cc: maxim.cournoyer@gmail.com
Subject: Re: weird OpenBLAS time-machine
Date: Thu, 03 Feb 2022 10:21:13 +0100 [thread overview]
Message-ID: <af3c9fb8c71fee557d9c41bf85318a83029a067c.camel@telenet.be> (raw)
In-Reply-To: <86r18k1ylf.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
zimoun schreef op do 03-02-2022 om 03:19 [+0100]:
> The issue is because concurrency. If two time-machines are run
> concurrently, they both update ~/.cache/guix/checkouts/ and the end
> result is hard to predict.
>
> Well, I probably ran inside one terminal “guix time-machine
> --commit=XXXX -- help” where XXXX a commit with openblas@0.3.9; and in
> the same time inside another terminal, “guix time-machine
> --commit=4b1538e6ef -- help”. Depending on “the same time”, the state
> of the checkout
> ~/.cache/guix/checkouts/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq
> used by the time-machine at 4b1538e6ef was the state for the commit
> XXXX.
>
> Then, all is messed!
FWIW it's a known issue but I can't find it on issues.guix.gnu.org.
The (unimplemented) fix is to use worktrees, or don't checkout and use
the libgit2 / (guix git) equivalent of
"git show 46fc72b2bfee2a30a3c3f3320e7d84b4b2fd646e some-file".
Greetings,
Maxime
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-02-03 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 17:00 weird OpenBLAS time-machine zimoun
2022-02-03 2:19 ` zimoun
2022-02-03 9:21 ` Maxime Devos [this message]
2022-02-03 10:42 ` zimoun
2022-02-03 12:20 ` Maxime Devos
2022-02-05 14:19 ` Ludovic Courtès
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: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=af3c9fb8c71fee557d9c41bf85318a83029a067c.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=zimon.toutoune@gmail.com \
/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://git.savannah.gnu.org/cgit/guix.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).