GNU bug report logs -
#57527
compute-guix-derivation has an error
Previous Next
To reply to this bug, email your comments to 57527 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#57527
; Package
guix
.
(Thu, 01 Sep 2022 15:35:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
"Toorn, H.W.P. van den (Henk)" <H.W.P.vandenToorn <at> uu.nl>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Thu, 01 Sep 2022 15:35:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Dear developers, the guix pull command ended in an error, and requested
to send the error to this e-mail.
Backtrace:
17 (primitive-load
"/gnu/store/vkwh34wlnqqfyf44giczcx848i3vdckr-compute-guix-derivation")
In ice-9/eval.scm:
155:9 16 (_ _)
159:9 15 (_ #(#(#(#(#(#(#(#(#(#(#(#(#(#(#(#(#<directory (guile-u?>
?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?))
In ice-9/boot-9.scm:
152:2 14 (with-fluid* _ _ _)
152:2 13 (with-fluid* _ _ _)
In ./guix/store.scm:
2168:24 12 (run-with-store #<store-connection 256.99 7f46aae43140>
#<procedure 7f469ec48690 at ./guix/self.scm:12?> ?)
1996:8 11 (_ #<store-connection 256.99 7f46aae43140>)
In ./guix/gexp.scm:
300:22 10 (_ #<store-connection 256.99 7f46aae43140>)
1181:2 9 (_ #<store-connection 256.99 7f46930e6e60>)
1047:2 8 (_ #<store-connection 256.99 7f46930e6e60>)
893:4 7 (_ #<store-connection 256.99 7f46930e6e60>)
In ./guix/store.scm:
2053:12 6 (_ #<store-connection 256.99 7f46930e6e60>)
1401:5 5 (map/accumulate-builds #<store-connection 256.99
7f46930e6e60> #<procedure 7f469414dda0 at ./guix/stor?> ?)
1417:15 4 (_ #<store-connection 256.99 7f46930e6e60>
("/gnu/store/4khcb3b0iqfimjgg6yqnlpf9pkim7s4v-curl-7.84.?" ?) ?)
1417:15 3 (loop #f)
711:11 2 (process-stderr #<store-connection 256.99 7f46930e6e60> _)
In ./guix/serialization.scm:
102:11 1 (read-int #<input-output: file 10>)
80:6 0 (get-bytevector-n* #<input-output: file 10> 8)
./guix/serialization.scm:80:6: In procedure get-bytevector-n*:
ERROR:
1. &nar-error:
file: #f
port: #<input-output: file 10>
guix pull: error: You found a bug: the program
'/gnu/store/vkwh34wlnqqfyf44giczcx848i3vdckr-compute-guix-derivation'
failed to compute the derivation for Guix (version:
"89d427e4be35fe79c23e2785a55c19df781fb77e"; system: "x86_64-linux";
host version: "fc94e93c4b60addfda3c1eddfb85907e9459a8af"; pull-version: 1).
Please report the COMPLETE output above by email to <bug-guix <at> gnu.org>.
--
Dr. Henk van den Toorn | Bioinformatician | Universiteit Utrecht |
Biomolecular Mass Spectrometry and Proteomics | Kruytgebouw, Padualaan
8, 3584 CH Utrecht | room O607 | (030) 253 67 58 | h.w.p.vandentoorn <at> uu.nl |
Information forwarded
to
bug-guix <at> gnu.org
:
bug#57527
; Package
guix
.
(Thu, 01 Sep 2022 16:40:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 57527 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
severity 57527 important
merge 47764 57527
thanks
For now, you can try working-around by retrying "guix pull".
On 01-09-2022 17:00, Toorn, H.W.P. van den (Henk) via Bug reports for
GNU Guix wrote:
> 1417:15 4 (_ #<store-connection 256.99 7f46930e6e60>
> ("/gnu/store/4khcb3b0iqfimjgg6yqnlpf9pkim7s4v-curl-7.84.?" ?) ?)
> 1417:15 3 (loop #f)
> 711:11 2 (process-stderr #<store-connection 256.99 7f46930e6e60> _)
> In ./guix/serialization.scm:
> 102:11 1 (read-int #<input-output: file 10>)
> 80:6 0 (get-bytevector-n* #<input-output: file 10> 8)
Procedure at 80:6:
> (define (get-bytevector-n* port count)
> (let ((bv (get-bytevector-n port count)))
> (when (or (eof-object? bv)
> (< (bytevector-length bv) count))
> (raise (condition (&nar-error
> (file (currently-restored-file))
> (port port)))))
> bv))
An alternative hypotheses:
* build-aux/build-self.scm lets the port be a duplicate of standard
input. But maybe some other code for whatever reason accidentally
reads from there as well? Or: maybe the script is started without
stdout, so when it is duplicated, it becomes stdout, and future code
writes to stdout (i.e., the store port), causing interference?
Potential solution: Open /dev/null on top of stdin, check that the
store port is >2.
Greetings,
Maxime.
[Message part 2 (text/html, inline)]
[OpenPGP_0x49E3EE22191725EE.asc (application/pgp-keys, attachment)]
[OpenPGP_signature (application/pgp-signature, attachment)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#57527
; Package
guix
.
(Thu, 01 Sep 2022 17:08:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 57527 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
severity 57527 important
merge 47764 57527
severity 53802 important
merge 47764 53802
severity 56466 important
merge 47764 56466
thanks
Found a few apparent duplicates (they are all about a &nar-error,
read-int and process-stderror).
On second thought, I don't think the patch I referred to #56466 will
help here, though it could hardly harm here.
For now, you can try working-around by retrying "guix pull".
There are two hypotheses on the cause in
* https://issues.guix.gnu.org/57527#1
* and https://issues.guix.gnu.org/47764
The second seems most plausible to me, and the first seems the simplest
to test (and even if it's not the cause, it would still add some
robustness).
Greetings,
Maxime.
[Message part 2 (text/html, inline)]
[OpenPGP_0x49E3EE22191725EE.asc (application/pgp-keys, attachment)]
[OpenPGP_signature (application/pgp-signature, attachment)]
Severity set to 'important' from 'normal'
Request was from
Maxime Devos <maximedevos <at> telenet.be>
to
control <at> debbugs.gnu.org
.
(Thu, 01 Sep 2022 17:08:02 GMT)
Full text and
rfc822 format available.
Merged 47764 47782 57527.
Request was from
Maxime Devos <maximedevos <at> telenet.be>
to
control <at> debbugs.gnu.org
.
(Thu, 01 Sep 2022 17:08:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#57527
; Package
guix
.
(Thu, 01 Sep 2022 17:39:01 GMT)
Full text and
rfc822 format available.
Message #20 received at 57527 <at> debbugs.gnu.org (full text, mbox):
Hi,
> For now, you can try working-around by retrying "guix pull".
Henk, could you retry
guix pull --commit=89d427e4be35fe79c23e2785a55c19df781fb77e
? BTW, it works for me with:
guix time-machine --commit=fc94e93c4b60addfda3c1eddfb85907e9459a8af \
-- time-machine --commit=89d427e4be35fe79c23e2785a55c19df781fb77e \
-- help
and I guess the error is transient because network.
What is the version of the daemon you are running?
Cheers,
simon
This bug report was last modified 2 years and 287 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.