unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: raingloom <raingloom@riseup.net>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Following Guix weather.
Date: Tue, 13 Apr 2021 02:04:36 +0200	[thread overview]
Message-ID: <20210413020436.53c922f1@riseup.net> (raw)
In-Reply-To: <87fszz1s42.fsf@gnu.org>

On Fri, 09 Apr 2021 15:53:49 +0200
Mathieu Othacehe <othacehe@gnu.org> wrote:

> Hello,
> 
> I have deployed a bunch of changes at https://ci.guix.gnu.org/. I'd
> like to introduce some of them here.
> 
> First, there are some new specifications: "images", "tarball" and
> "tests".  Those specifications are configured to build respectively,
> the %guix-system-images declared in (gnu ci), the Guix binary tarball
> and the Guix System tests.
> 
> Each Guix commit potentially triggers a rebuilt of all those
> specifications. We have previously established that this is too
> resource consuming.
> 
> That's why I have added a "period" field to the specification
> definition.  This field only allows a new evaluation when at least X
> seconds have elapsed since the last evaluation.  Right now, the three
> aforementioned specifications have a period field set to 86400 seconds
> (24 hours).
> 
> I have also improved the visibility of latest state of a
> specification. For instance, if you want to know what's the current
> status of the "master" branch or the "staging" branch, you will find
> some statistics directly on the home page. For a more detailed view,
> you can consult dashboards for each specification.
> 
> master dashboard: https://ci.guix.gnu.org/eval/19534/dashboard
> staging dashboard: https://ci.guix.gnu.org/eval/19488/dashboard
> test dashboard: https://ci.guix.gnu.org/eval/19464/dashboard
> 
> By having a look at those dashboards, it's obvious that we still have
> a lot of work before all those circles turn to green.
> 
> Finally, in the evaluation view there's a "Toggle" button to switch
> between:
> 
> - The number of newly fixed/broken/pending builds for each evaluation
>   (default)
> - The total number of fixed/broken/pending builds for each evaluation.
> 
> Don't hesitate to comment on those new features :)
> 
> Thanks,
> 
> Mathieu
> 
> 

Speaking of visibility, please don't use color as the sole carrier of
information. I don't know if you did any accessibility testing for that
page, but not requiring perfect color vision should be step 0. Luckily
it should be an easy fix, just use some shapes.


      parent reply	other threads:[~2021-04-13  0:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 13:53 Following Guix weather Mathieu Othacehe
2021-04-09 17:09 ` Pierre Neidhardt
2021-04-09 19:28   ` Vincent Legoll
2021-04-09 19:38     ` Mathieu Othacehe
2021-04-09 20:09       ` Vincent Legoll
2021-04-13  0:04 ` raingloom [this message]

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=20210413020436.53c922f1@riseup.net \
    --to=raingloom@riseup.net \
    --cc=guix-devel@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).