compute-guix-derivation has an error

  • Open
  • quality assurance status badge
Details
3 participants
  • Toorn, H.W.P. van den (Henk)
  • Maxime Devos
  • zimoun
Owner
unassigned
Submitted by
Toorn, H.W.P. van den (Henk)
Severity
important
Merged with
T
T
Toorn, H.W.P. van den (Henk) wrote on 1 Sep 2022 17:00
(name . bug-guix@gnu.org)(address . bug-guix@gnu.org)
4a7379ce-40b6-0a56-648c-8160cd1cf1b6@uu.nl
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@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@uu.nl |
M
M
Maxime Devos wrote on 1 Sep 2022 18:39
c31526e0-eec1-2a76-409e-a22e5b3438a5@telenet.be
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:
Toggle quote (7 lines)
>   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:
Toggle quote (8 lines)
> (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.
Attachment: file
Attachment: OpenPGP_signature
M
M
Maxime Devos wrote on 1 Sep 2022 19:07
59cb7f24-d9c8-5394-cdbd-605d5addd03a@telenet.be
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
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.
Attachment: file
Attachment: OpenPGP_signature
Z
Z
zimoun wrote on 1 Sep 2022 19:38
86pmgf3shh.fsf@gmail.com
Hi,

Toggle quote (2 lines)
> 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
?
Your comment

Commenting via the web interface is currently disabled.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 57527
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