IRC channel logs
2023-11-23.log
back to list of logs
<bilke>I have set up a cuirass server and added a build specification. It evaluates and creates some build jobs but they only show up as scheduled in the web ui. In the logs I only found this: <bilke>2023-11-21 15:52:45 evaluation 97450 for 'ogs' completed <bilke>2023-11-21 15:52:45 evaluation 97450 of jobset 'ogs' registered 13 builds <bilke>2023-11-21 15:52:45 building 13 derivations in batches of 200 <bilke>2023-11-21 15:52:45 building batch of 200 derivations (0/13) <bilke>2023-11-21 15:52:45 Uncaught exception in task: <bilke>2023-11-21 15:52:45 In fibers.scm: <bilke>2023-11-21 15:52:45 172:8 8 (_) <bilke>2023-11-21 15:52:45 In ice-9/boot-9.scm: <bilke>2023-11-21 15:52:45 1752:10 7 (with-exception-handler _ _ #:unwind? _ # _) <bilke>2023-11-21 15:52:45 In guix/store.scm: <bilke>2023-11-21 15:52:45 659:37 6 (thunk) <bilke>2023-11-21 15:52:45 In cuirass/base.scm: <bilke>2023-11-21 15:52:45 421:14 5 (_ _) <bilke>2023-11-21 15:52:45 267:10 4 (spawn-builds #<store-connection 256.99 7f64872676e0> _ ?) <bilke>2023-11-21 15:52:45 In ice-9/boot-9.scm: <bilke>2023-11-21 15:52:45 1752:10 3 (with-exception-handler _ _ #:unwind? _ # _) <bilke>2023-11-21 15:52:45 1685:16 2 (raise-exception _ #:continuable? _) <bilke>2023-11-21 15:52:45 1683:16 1 (raise-exception _ #:continuable? _) <bilke>2023-11-21 15:52:45 1685:16 0 (raise-exception _ #:continuable? _) <bilke>2023-11-21 15:52:45 ice-9/boot-9.scm:1685:16: In procedure raise-exception: <bilke>2023-11-21 15:52:45 In procedure struct-vtable: Wrong type argument in position 1 (expecting struct): #f <bilke>Any idea what I can do to let the builds run? <zimoun>civodul: Well, my new laptop have some AMD GPU, I guess… since I have “kernel: amd_gpio AMDI0030:00: Invalid config param 0014” with some Linux kernel. <zimoun>Is it something useful for testing the ROCm Merge Request? <civodul>zimoun: it may be! i’m not super knowledgeable i must say <civodul>bilke: hi! apparently you’re using the default build backend, which is unfortunately not as much tested as the “remote-server” mechanism <civodul>if you’re distributing builds on several machines, i strongly recommend the remote-server thing <civodul>if not, could you please report the issue to bug-guix@gnu.org? <bilke>civodul: Thanks, will try a remote worker setup first...