From: Bengt Richter <bokr@bokr.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 47496@debbugs.gnu.org
Subject: bug#47496: Very slow `guix environment -l nyxt/build-scripts/guix.scm
Date: Sun, 4 Apr 2021 04:08:08 +0200 [thread overview]
Message-ID: <20210404020808.GA10840@LionPure> (raw)
In-Reply-To: <87mtufp5vj.fsf@ambrevar.xyz>
Hi,
On +2021-04-03 20:42:08 +0200, Pierre Neidhardt wrote:
> I just tried the following:
>
> --8<---------------cut here---------------start------------->8---
> guix environment -l ...
> --8<---------------cut here---------------end--------------->8---
>
> was forever until I stopped it.
> Then
>
>
> --8<---------------cut here---------------start------------->8---
> guix environment --no-grafts -l ...
> --8<---------------cut here---------------end--------------->8---
>
> completed in a few seconds.
>
> After this,
>
> --8<---------------cut here---------------start------------->8---
> guix environment -l ...
> --8<---------------cut here---------------end--------------->8---
>
> again completed in just a few seconds too.
>
Could bash have cached a reference somwhere that made the difference?
If you are running in bash, type
hash
to get a listing of things it has hash-table reference to
see also help bash (unless your shell context is different, in which case,
for convenience, the expected output is:
--8<---------------cut here---------------start------------->8---
hash: hash [-lr] [-p pathname] [-dt] [name ...]
Remember or display program locations.
Determine and remember the full pathname of each command NAME. If
no arguments are given, information about remembered commands is displayed.
Options:
-d forget the remembered location of each NAME
-l display in a format that may be reused as input
-p pathname use PATHNAME as the full pathname of NAME
-r forget all remembered locations
-t print the remembered location of each NAME, preceding
each location with the corresponding NAME if multiple
NAMEs are given
Arguments:
NAME Each NAME is searched for in $PATH and added to the list
of remembered commands.
Exit Status:
Returns success unless NAME is not found or an invalid option is given.
--8<---------------cut here---------------end--------------->8---
Usually this bites me by keeping on doing something old in spite of PATH changes,
but if "something old" got established by your
> --8<---------------cut here---------------start------------->8---
> guix environment --no-grafts -l ...
> --8<---------------cut here---------------end--------------->8---
maybe it could have gotten hash-cached and remembered to make
--8<---------------cut here---------------start------------->8---
> guix environment -l ...
> --8<---------------cut here---------------end--------------->8---
> "work" ??
Anyway, apparently some state change is "remembered" in your sequence above,
so I was reminded :)
> --
> Pierre Neidhardt
> https://ambrevar.xyz/
--
Regards,
Bengt Richter
prev parent reply other threads:[~2021-04-04 2:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 10:02 bug#47496: Very slow `guix environment -l nyxt/build-scripts/guix.scm Pierre Neidhardt
2021-04-02 7:43 ` Ludovic Courtès
2021-04-02 8:14 ` Pierre Neidhardt
2021-04-03 18:42 ` Pierre Neidhardt
2021-04-04 2:08 ` Bengt Richter [this message]
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=20210404020808.GA10840@LionPure \
--to=bokr@bokr.com \
--cc=47496@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
/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).