all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: david larsson <david.larsson@selfhosted.xyz>
Cc: 44390@debbugs.gnu.org
Subject: bug#44390: Cuirass reports succesful builds as failed in /var/log/cuirass.log and cuirass-web reports them as scheduled
Date: Mon, 02 Nov 2020 17:28:48 +0100	[thread overview]
Message-ID: <875z6nbu4f.fsf@gnu.org> (raw)
In-Reply-To: <cc108f951ebe6680eb4f627a12770568@selfhosted.xyz> (david larsson's message of "Mon, 02 Nov 2020 15:04:31 +0000")


Hello David,

> /gnu/store/4ijsrmkb02z2s18bgkw5kyvf4kpwsdyg-python-pydotplus-2.0.2
> 2020-11-02T15:42:20 success: 0, fail: 10
> 2020-11-02T15:42:34 heap: 44.49 MiB; threads: 11; file descriptors: 4

Thanks for the bug report. This bug is the result of some recent
optimizations. The database requests updating the build statuses are
queued and issues by batches of 100 requests.

As you only have 10 builds, those requests are only queued. That's why
the web interface reports them as "scheduled" while the log shows that
they were built.

The "fail: 10" is also a consequence of that problem. Forcing the
pending queries once a batch of builds is done could possibly solve this
problem but I need to think more about it.

Thanks,

Mathieu




  reply	other threads:[~2020-11-02 16:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 15:04 bug#44390: Cuirass reports succesful builds as failed in /var/log/cuirass.log and cuirass-web reports them as scheduled david larsson
2020-11-02 16:28 ` Mathieu Othacehe [this message]
2020-11-02 16:40 ` Jonathan Brielmaier
2020-11-06 14:07 ` Jonathan Brielmaier
2020-12-06  9:16   ` david larsson
2020-12-08 11:09     ` Mathieu Othacehe
2020-12-08 22:35       ` Jonathan Brielmaier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875z6nbu4f.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=44390@debbugs.gnu.org \
    --cc=david.larsson@selfhosted.xyz \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.