"guix pull error: You found a bug"

  • Open
  • quality assurance status badge
Details
2 participants
  • Pierre-Henry Fröhring
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Pierre-Henry Fröhring
Severity
normal
P
P
Pierre-Henry Fröhring wrote on 4 Mar 2022 22:35
(address . bug-guix@gnu.org)
27984ea7e48296e328d7141bb674a86ff2687817.camel@phfrohring.com
Hello,

I've done as the comment says i.e. reporting the bug.

# guix pull
Updating channel 'guix' from Git repository at
Authenticating channel 'guix', commits 9edb3f6 to d049ff1 (3 new
commits)...
Building from this channel:
substitute: updating substitutes from 'https://ci.guix.gnu.org'...
100.0%
substitute: updating substitutes from
'https://bordeaux.guix.gnu.org'... 100.0%
building /gnu/store/23f7vvgb33h19h89j01jqiz86c6indy2-compute-guix-
derivation.drv...
Computing Guix derivation for 'x86_64-linux'... \guix pull: error: You
found a bug: the program '/gnu/store/6yhwysy1x5zc5s4xbdar2sayqc20fwdl-
compute-guix-derivation'
failed to compute the derivation for Guix (version:
"d049ff159980954dccb6bc578b1df1efbc408e92"; system: "x86_64-linux";
host version: "218400c0f7d754467eac20bbdea3c5282efe7b2e"; pull-version:
1).
Please report the COMPLETE output above by email to <bug-guix@gnu.org>.


Regards,
phf
M
M
Maxim Cournoyer wrote on 5 Mar 2022 04:40
(name . Pierre-Henry Fröhring)(address . contact@phfrohring.com)(address . 54247@debbugs.gnu.org)
87a6e512zd.fsf@gmail.com
Hi Pierre,

Pierre-Henry Fröhring <contact@phfrohring.com> writes:

Toggle quote (26 lines)
> Hello,
>
> I've done as the comment says i.e. reporting the bug.
>
> # guix pull
> Updating channel 'guix' from Git repository at
> 'https://git.savannah.gnu.org/git/guix.git'...
> Authenticating channel 'guix', commits 9edb3f6 to d049ff1 (3 new
> commits)...
> Building from this channel:
> guix https://git.savannah.gnu.org/git/guix.git d049ff1
> substitute: updating substitutes from 'https://ci.guix.gnu.org'...
> 100.0%
> substitute: updating substitutes from
> 'https://bordeaux.guix.gnu.org'... 100.0%
> building /gnu/store/23f7vvgb33h19h89j01jqiz86c6indy2-compute-guix-
> derivation.drv...
> Computing Guix derivation for 'x86_64-linux'... \guix pull: error: You
> found a bug: the program '/gnu/store/6yhwysy1x5zc5s4xbdar2sayqc20fwdl-
> compute-guix-derivation'
> failed to compute the derivation for Guix (version:
> "d049ff159980954dccb6bc578b1df1efbc408e92"; system: "x86_64-linux";
> host version: "218400c0f7d754467eac20bbdea3c5282efe7b2e"; pull-version:
> 1).
> Please report the COMPLETE output above by email to <bug-guix@gnu.org>.

Thanks for the report.

It appears this happened while ci.guix.gnu.org (Cuirass) was down; I
wonder what the error was though. Could you please try the following:

Toggle snippet (3 lines)
$ guix build /gnu/store/6yhwysy1x5zc5s4xbdar2sayqc20fwdl-compute-guix-derivation

To retry building the problematic derivation? And attach the full
compressed log here.

Thank you,

Maxim
P
P
Pierre-Henry Fröhring wrote on 5 Mar 2022 11:23
(name . Maxim Cournoyer)(address . maxim.cournoyer@gmail.com)(address . 54247@debbugs.gnu.org)
a49c1ff92265efd3b3e7050d49f7c5b68f9df51f.camel@phfrohring.com
Thanks for the report.

It appears this happened while ci.guix.gnu.org (Cuirass) was down; I wonder
what the error was though. Could you please try the following:

–8<—————cut here—————start————->8— $ guix build
/gnu/store/6yhwysy1x5zc5s4xbdar2sayqc20fwdl-compute-guix-derivation
–8<—————cut here—————end—————>8—

To retry building the problematic derivation? And attach the full compressed
log here.

Thank you,

Maxim

Thank you for the swift answer Maxim. Executing :

?????
? guix build /gnu/store/6yhwysy1x5zc5s4xbdar2sayqc20fwdl-compute-guix-derivation
?????

yielded nothing.

Executing :

?????
? guix pull
?????

yielded the same result as above.

I resized the tiny VPS to a bigger one just above and it worked. Here is the new "size" of
the VPS :

Basic - Premium AMD, Shared CPU, 1 vCPU, 2 GB, 25 GB, 2 TB

May I suggest a kind of warning or test for hardware requirements when `guix' is used ?

Thank you, PHF
M
M
Maxim Cournoyer wrote on 7 Mar 2022 03:38
(name . Pierre-Henry Fröhring)(address . contact@phfrohring.com)
87mti2zdtu.fsf@gmail.com
Hello,

Pierre-Henry Fröhring <contact@phfrohring.com> writes:

Toggle quote (37 lines)
> Thanks for the report.
>
> It appears this happened while ci.guix.gnu.org (Cuirass) was down; I wonder
> what the error was though. Could you please try the following:
>
> –8<—————cut here—————start————->8— $ guix build
> /gnu/store/6yhwysy1x5zc5s4xbdar2sayqc20fwdl-compute-guix-derivation
> –8<—————cut here—————end—————>8—
>
> To retry building the problematic derivation? And attach the full compressed
> log here.
>
> Thank you,
>
> Maxim
>
> Thank you for the swift answer Maxim. Executing :
>
> ?????
> ? guix build /gnu/store/6yhwysy1x5zc5s4xbdar2sayqc20fwdl-compute-guix-derivation
> ?????
>
> yielded nothing.
>
> Executing :
>
> ?????
> ? guix pull
> ?????
>
> yielded the same result as above.
>
> I resized the tiny VPS to a bigger one just above and it worked. Here is the new "size" of
> the VPS :
>
> Basic - Premium AMD, Shared CPU, 1 vCPU, 2 GB, 25 GB, 2 TB

Glad it worked now. What was the original system specifications? I
suspect a lack of RAM, perhaps.

Toggle quote (2 lines)
> May I suggest a kind of warning or test for hardware requirements when `guix' is used ?

That's a good suggestion, but I'm guessing difficult to implement ('guix
pull' may complete with very little memory used or a lot, depending on
the availability of substitutes).

For you specific needs (low specs), I'd suggest using this your
~/.config/guix/channels.scm file:

Toggle snippet (7 lines)
(use-modules (guix ci))

(list (channel-with-substitutes-available
%default-guix-channel
"https://ci.guix.gnu.org"))

As documented in '(guix) Channels with Substitutes'.

I hope that helps,

Maxim
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 54247@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 54247
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch