Hi Simon & Tobias, Ludovic Courtès <l...@gnu.org> skribis:
> Tobias Geerinckx-Rice <m...@tobias.gr> skribis: > >> Simon Streit 写道： >>> ice-9/boot-9.scm:1685:16: In procedure raise-exception: >>> no code for module (system repl error-handling) >> >> Thank you for reporting this. With commit >> 5fa46ca96da90ec19e32cc4d726f099d0979d60b on master, the system >> tests that failed for me with this error no longer do. > > What system tests were failing? > > At first sight I don’t see how a67c00f4f7ee0a70fce14a7e1907cce332c85813 > led to this: > > activating system... > Backtrace: > In ice-9/boot-9.scm: > 3422:24 19 (_) > 222:29 18 (map1 (((gnu system accounts)) ((gnu build accounts)) …)) > 222:29 17 (map1 (((gnu build accounts)) ((gnu build #)) ((# …)) …)) > 222:17 16 (map1 (((gnu build linux-boot)) ((guix build utils)) # …)) > 3326:17 15 (resolve-interface (gnu build linux-boot) #:select _ # _ …) > In ice-9/threads.scm: > 390:8 14 (_ _) > In ice-9/boot-9.scm: > 3252:13 13 (_) > In ice-9/threads.scm: > 390:8 12 (_ _) > In ice-9/boot-9.scm: > 3536:20 11 (_) > 2835:4 10 (save-module-excursion #<procedure 7f9a73ee5b70 at ice-…>) > 3556:26 9 (_) > In unknown file: > 8 (primitive-load-path "gnu/build/linux-boot" #<procedure…>) > In gnu/build/linux-boot.scm: > 22:0 7 (_) > In ice-9/boot-9.scm: > 3409:4 6 (define-module* _ #:filename _ #:pure _ #:version _ # _ …) > 3422:24 5 (_) > 222:29 4 (map1 (((rnrs io ports)) ((system repl #)) ((srfi #)) …)) > 222:17 3 (map1 (((system repl error-handling)) ((srfi srfi-1)) …)) > 3329:6 2 (resolve-interface (system repl error-handling) #:select …) > 1685:16 1 (raise-exception _ #:continuable? _) > 1685:16 0 (raise-exception _ #:continuable? _) > > ice-9/boot-9.scm:1685:16: In procedure raise-exception: > no code for module (system repl error-handling) I’ve tried several system tests and manually running a system in a VM, with a67c00f4f7ee0a70fce14a7e1907cce332c85813 reinstated, and cannot reproduce the issue. Do you know of a way to reproduce it? The IRC log <https://logs.guix.gnu.org/guix/2021-05-18.log> suggests that a couple of people experienced the issue on that day, but pastes are no longer accessible. TIA! Ludo’.
