From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: bug#32575: [Cuirass] Filter results by architecture Date: Thu, 30 Aug 2018 11:41:35 +0200 Message-ID: <20180830114135.3226977f@scratchpost.org> References: <87a7p5b7x3.fsf@elephly.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/2_rap=0mFg/EgkvPqmmFk9q"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33785) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fvJbI-000326-T0 for bug-guix@gnu.org; Thu, 30 Aug 2018 05:50:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fvJSk-0004as-KH for bug-guix@gnu.org; Thu, 30 Aug 2018 05:42:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:32893) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fvJSk-0004aY-6E for bug-guix@gnu.org; Thu, 30 Aug 2018 05:42:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fvJSj-0004YU-RN for bug-guix@gnu.org; Thu, 30 Aug 2018 05:42:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87a7p5b7x3.fsf@elephly.net> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ricardo Wurmus Cc: 32575@debbugs.gnu.org --Sig_/2_rap=0mFg/EgkvPqmmFk9q Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Ricardo, On Wed, 29 Aug 2018 15:54:47 +0200 Ricardo Wurmus wrote: > The Cuirass web interface shows the number of successful, failed, and > pending builds for each evaluation. Looking at just these numbers it is > impossible to tell, how each of the supported architectures is affected. >=20 > It would be good if we could separate the view by architecture. Then we > could more easily determine that a change broke many builds for one > architecture while fixing builds on another. >=20 > One way to do this would be to accept an optional query variable, e.g. >=20 > http://ci.guix.info/jobset/guix-master?system=3Dx86_64-linux >=20 > This could be selected from a drop-down on the page or exposed through a > number of links. I agree. Also, in the Javascript frontend I had a list of architecture links for eac= h package. The filter could be applied to show only a given set of architectures. I think that for a portable package, the architecture it runs on is an implementation detail - it should build on all of them. If it doesn't, that should show up as an error. So I had hello [x86_64-checkbox-log] [armhf-checkbox-log] [aarch64-checkbox-l= og] and not hello.x86_64 [checkbox-log] hello.armhf [checkbox-log] hello.aarch64 [checkbox-log] The latter looks more like these are different packages with different purp= oses - which they really aren't from a user standpoint. --Sig_/2_rap=0mFg/EgkvPqmmFk9q Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAluHu88ACgkQ5xo1VCww uqUDggf/dGwlrLue5DFX1bMxEPFoMV2jdtCrHg8C3NwTEzPP8S7pMaTjpLlLgMCB N++/J0ubPN0eqlXpkcDZvmM2SPH8udyWxXZH7poyhpZdgHCYcBb/NIl8Lp90M8gj dRy2tlw/JvfUewUfPFa675HpNObDTs+D4+0v5eZMNWXZLIHxX18CtGkFSAHbEbrm 7Kovp05JcOcP8mnOIZlNYlTSBa9UIfQGZMLvWRjQaITxgW3WDCUJ7dnB4VqAk8FG sgq/vFa2BPGbZ8bY/8VWB/7IwbjhPQDFTu1f0usWSULM/hDJDdWYW84PyZ7AcIc+ bolnT51hOOvSZoO0aFifgkIvo3oj+g== =nq/T -----END PGP SIGNATURE----- --Sig_/2_rap=0mFg/EgkvPqmmFk9q--