From: Mark H Weaver <mhw@netris.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: Merging staging?
Date: Wed, 09 Jan 2019 14:15:56 -0500 [thread overview]
Message-ID: <87h8eh7ibc.fsf@netris.org> (raw)
In-Reply-To: <20190109162729.GA18849@macbook41> (Efraim Flashner's message of "Wed, 9 Jan 2019 18:27:29 +0200")
Hi Efraim,
Efraim Flashner <efraim@flashner.co.il> writes:
> I merged master into staging today and got the following chart:
>
> | architecture | berlin | hydra |
> +--------------+--------+-------+
> | x86_64 | 42.2% | 78.8% |
> | i686 | 28.2% | 64.3% |
> | aarch64 | 0% | 23.0% |
> | armhf | 16.8% | 50.4% |
>
> but compared to master:
>
> | architecture | berlin | hydra |
> +--------------+--------+-------+
> | x86_64 | 57.5% | 91.9% |
> | i686 | 44.4% | 77.8% |
> | aarch64 | 0% | 41.8% |
> | armhf | 30.3% | 69.6% |
Something looks wrong here, because Hydra has never supported aarch64,
i.e. it does not create jobs for that system and has never been
connected to an aarch64 build slave, so I don't see how it could
possibly have more than 0% coverage on that system.
> So I think I'd like to see a comparison on hydra of staging vs master
> and if it's good enough we go ahead and merge
I just asked Hydra to produce another evaluation of 'staging'. When it
has finished doing so, we'll know more.
Thanks!
Mark
next prev parent reply other threads:[~2019-01-09 19:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 14:58 Merging staging? Julien Lepiller
2018-12-20 18:36 ` Mark H Weaver
2018-12-20 22:45 ` Julien Lepiller
2018-12-21 1:17 ` Mark H Weaver
2018-12-21 9:06 ` Gábor Boskovits
2018-12-21 23:06 ` Ludovic Courtès
2018-12-23 14:00 ` Efraim Flashner
2019-01-09 16:27 ` Efraim Flashner
2019-01-09 19:15 ` Mark H Weaver [this message]
2019-01-09 19:27 ` Efraim Flashner
2019-01-10 2:27 ` Mark H Weaver
2019-01-10 22:04 ` Ludovic Courtès
2019-01-09 21:51 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2022-06-01 8:35 Release v1.4? zimoun
2022-06-03 16:41 ` Ludovic Courtès
2022-06-06 21:17 ` Merging ‘staging’? Ludovic Courtès
2022-06-08 11:50 ` Efraim Flashner
2022-06-08 21:24 ` Ludovic Courtès
2022-06-10 7:57 ` Efraim Flashner
2022-06-11 9:53 ` Ludovic Courtès
2022-06-11 10:49 ` Tom Fitzhenry
2022-06-12 3:58 ` Efraim Flashner
2022-06-12 21:08 ` Ludovic Courtès
2022-06-13 7:03 ` Ludovic Courtès
2022-06-14 4:01 ` Thiago Jung Bauermann
2022-06-09 17:19 ` pelzflorian (Florian Pelz)
2022-06-09 17:41 ` Efraim Flashner
2022-06-09 19:02 ` pelzflorian (Florian Pelz)
2022-06-10 6:07 ` pelzflorian (Florian Pelz)
2022-06-11 7:35 ` pelzflorian (Florian Pelz)
2022-06-12 4:54 ` Thiago Jung Bauermann
2022-06-12 21:06 ` 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=87h8eh7ibc.fsf@netris.org \
--to=mhw@netris.org \
--cc=efraim@flashner.co.il \
--cc=guix-devel@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).