From: Mathieu Othacehe <othacehe@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 32548-done@debbugs.gnu.org
Subject: bug#32548: Cuirass: Performance monitoring
Date: Thu, 17 Sep 2020 12:07:49 +0200 [thread overview]
Message-ID: <877dss90ne.fsf@gnu.org> (raw)
In-Reply-To: <87o8m8b1l8.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 14 Sep 2020 21:27:47 +0200")
Hey Ludo,
> As discussed on IRC, builds per day should be compared to new
> derivations per day. For example, if on a day there’s 100 new
> derivations and we only manage to build 10 of them, we have a problem.
I added this line, and they sadly do not overlap :(
> 2020-09-14T21:16:21 Failed to compute metric average-eval-duration-per-spec (version-1.1.0).
> 2020-09-14T21:16:21 Failed to compute metric average-10-last-eval-duration-per-spec (wip-desktop).
> 2020-09-14T21:16:21 Failed to compute metric average-100-last-eval-duration-per-spec (wip-desktop).
> 2020-09-14T21:16:21 Failed to compute metric average-eval-duration-per-spec (wip-desktop).
>
> Perhaps it can’t compute an average yet for these jobsets?
Yes as soon as those evaluations will be repaired, we should be able to
compute those metrics. I chose to keep the error messages as a
remainder.
I added various other metrics and updated the "/metrics" page. Once we
have a better view, we should think of adding thresholds on those
metrics.
Closing this one!
Thanks,
Mathieu
--
https://othacehe.org
next prev parent reply other threads:[~2020-09-17 10:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 22:33 bug#32548: Cuirass: Performance monitoring Ludovic Courtès
2020-09-06 14:42 ` Mathieu Othacehe
2020-09-06 18:51 ` Christopher Baines
2020-09-07 8:11 ` Ludovic Courtès
2020-09-10 13:26 ` Mathieu Othacehe
2020-09-14 13:34 ` Mathieu Othacehe
2020-09-14 14:10 ` zimoun
2020-09-16 2:21 ` Bonface M. K.
2020-09-14 19:27 ` Ludovic Courtès
2020-09-17 10:07 ` Mathieu Othacehe [this message]
2020-09-17 20:22 ` Ludovic Courtès
2020-09-16 15:56 ` Andreas Enge
2020-09-17 7:10 ` Mathieu Othacehe
2020-09-18 12:21 ` 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=877dss90ne.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=32548-done@debbugs.gnu.org \
--cc=ludo@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).