From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 43565@debbugs.gnu.org
Subject: bug#43565: cuirass: Fibers scheduling blocked.
Date: Mon, 05 Oct 2020 14:13:19 +0200 [thread overview]
Message-ID: <87r1qc27mo.fsf@gnu.org> (raw)
In-Reply-To: <87eemtzr1q.fsf@gnu.org> (Mathieu Othacehe's message of "Tue, 22 Sep 2020 18:58:57 +0200")
Hi,
Mathieu Othacehe <othacehe@gnu.org> 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 'core-updates-core-updates'
> 2020-09-22T04:04:25 build succeeded: '/gnu/store/c7m6jxdkyjs7m5ynavagjwgp172a3xzv-partition.img.drv'
> waiting for the big garbage collector lock...
> ...
> 2020-09-22T10:36:02 fetching input 'guix' of spec 'guix-master'
>
> A potential cause is described here:
> https://issues.guix.gnu.org/43552#1.
‘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.
Ludo’.
next prev parent reply other threads:[~2020-10-05 12:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 16:58 bug#43565: cuirass: Fibers scheduling blocked Mathieu Othacehe
2020-10-05 12:13 ` Ludovic Courtès [this message]
2020-10-22 11:55 ` Mathieu Othacehe
2020-10-23 12:21 ` Ludovic Courtès
2020-10-26 14:22 ` Mathieu Othacehe
2020-10-26 16:20 ` Ludovic Courtès
2020-10-27 18:03 ` Mathieu Othacehe
2020-11-02 10:09 ` Mathieu Othacehe
2020-11-19 10:56 ` Mathieu Othacehe
2020-11-20 8:37 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1qc27mo.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=43565@debbugs.gnu.org \
--cc=othacehe@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).