bug#43565: cuirass: Fibers scheduling blocked.

2020-11-20 Thread Ludovic Courtès
Hi, Mathieu Othacehe skribis: >> In cuirass/utils.scm: >>320:22 1 (_) >> In unknown file: >>0 (make-stack #t) >> ERROR: In procedure make-stack: >> In procedure struct-vtable: Wrong type argument in position 1 (expecting >> struct): #f > > I think this error is caused by settin

bug#43565: cuirass: Fibers scheduling blocked.

2020-11-19 Thread Mathieu Othacehe
Hey, > In cuirass/utils.scm: >320:22 1 (_) > In unknown file: >0 (make-stack #t) > ERROR: In procedure make-stack: > In procedure struct-vtable: Wrong type argument in position 1 (expecting > struct): #f I think this error is caused by setting: --8<---cut here

bug#43565: cuirass: Fibers scheduling blocked.

2020-11-02 Thread Mathieu Othacehe
Hey, > Yeah please go ahead if you want, or let me know if you’d rather let me > apply it. I finally reverted this patch that causes the following error: --8<---cut here---start->8--- 2020-11-02T11:05:08 fatal: uncaught exception 'wrong-type-arg' in 'build'

bug#43565: cuirass: Fibers scheduling blocked.

2020-10-27 Thread Mathieu Othacehe
Hey, > Yeah please go ahead if you want, or let me know if you’d rather let me > apply it. I applied your patch, thanks! I'm closing this one, because there's nothing much that can be done right now. Thanks, Mathieu

bug#43565: cuirass: Fibers scheduling blocked.

2020-10-26 Thread Ludovic Courtès
Hello! Mathieu Othacehe skribis: >> But does Cuirass create file descriptors as O_NONBLOCK? This has to be >> done explicitly, Fibers won’t do it for us. As it turns out, the answer >> is no, in at least one important case: the connection to the daemon >> (untested patch below). >> >> While GC

bug#43565: cuirass: Fibers scheduling blocked.

2020-10-26 Thread Mathieu Othacehe
Hey! Many thanks for your help, you rock! > But does Cuirass create file descriptors as O_NONBLOCK? This has to be > done explicitly, Fibers won’t do it for us. As it turns out, the answer > is no, in at least one important case: the connection to the daemon > (untested patch below). > > Whil

bug#43565: cuirass: Fibers scheduling blocked.

2020-10-23 Thread Ludovic Courtès
Good afternoon fearless hacker! Mathieu Othacehe skribis: >> ‘process-build-log’ in Cuirass uses ‘read-line/non-blocking’ to read a >> line from the log port of ‘build-derivations&’. If that really is >> non-blocking (and I think it is), then we should be fine? >> >> We should attach GDB to Cui

bug#43565: cuirass: Fibers scheduling blocked.

2020-10-22 Thread Mathieu Othacehe
Hey Ludo! > ‘process-build-log’ in Cuirass uses ‘read-line/non-blocking’ to read a > line from the log port of ‘build-derivations&’. If that really is > non-blocking (and I think it is), then we should be fine? > > We should attach GDB to Cuirass next time to see what’s blocking. Cuirass is cu

bug#43565: cuirass: Fibers scheduling blocked.

2020-10-05 Thread Ludovic Courtès
Hi, Mathieu Othacehe skribis: > Today between 04:04 and 10:36 no inputs were fetched. Fetching is > supposed to happen every 5 minutes. This seem to be correlated to the > duration of the garbage collection happening on berlin. > > 2020-09-22T04:04:23 fetching input 'core-updates' of spec > 'co

bug#43565: cuirass: Fibers scheduling blocked.

2020-09-22 Thread Mathieu Othacehe
Hello, Today between 04:04 and 10:36 no inputs were fetched. Fetching is supposed to happen every 5 minutes. This seem to be correlated to the duration of the garbage collection happening on berlin. --8<---cut here---start->8--- 2020-09-22T04:04:23 fetching i