From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mark H Weaver <mhw@netris.org>
Subject: Re: Merging staging?
Date: Wed, 09 Jan 2019 14:15:56 -0500
Message-ID: <87h8eh7ibc.fsf@netris.org>
References: <c8b84a082fc98eb3175172374a1bfcf3@lepiller.eu>
	<20181223140048.GE2581@macbook41> <20190109162729.GA18849@macbook41>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([209.51.188.92]:33640)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mhw@netris.org>) id 1ghJLc-0004Hn-5o
	for guix-devel@gnu.org; Wed, 09 Jan 2019 14:17:04 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mhw@netris.org>) id 1ghJLb-0001go-Gn
	for guix-devel@gnu.org; Wed, 09 Jan 2019 14:17:04 -0500
Received: from world.peace.net ([64.112.178.59]:59904)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <mhw@netris.org>) id 1ghJLb-0001g8-Da
	for guix-devel@gnu.org; Wed, 09 Jan 2019 14:17:03 -0500
In-Reply-To: <20190109162729.GA18849@macbook41> (Efraim Flashner's message of
	"Wed, 9 Jan 2019 18:27:29 +0200")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org

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