unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 32575@debbugs.gnu.org, clement@lassieur.org
Subject: bug#32575: [Cuirass] Filter results by architecture
Date: Thu, 30 Aug 2018 14:14:07 +0200	[thread overview]
Message-ID: <87efegxd9s.fsf@gnu.org> (raw)
In-Reply-To: <20180830114135.3226977f@scratchpost.org> (Danny Milosavljevic's message of "Thu, 30 Aug 2018 11:41:35 +0200")

Hi Danny & all,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> 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-log]
>
> 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 purposes -
> which they really aren't from a user standpoint.

The difficulty is that, from Cuirass’ viewpoint, “hello.x86_64-linux”
and “hello.armhf-linux” are just two different unrelated jobs.

Perhaps what we would need is to internally change how jobs are
represented in the database: we could have one job, “hello”, connected
to one or more “builds”, each with its own system.

I think it would amount to splitting the “Builds” table into two tables:
“Builds” and “Jobs”.  Clément, does that make sense?

Ludo’.

  reply	other threads:[~2018-08-30 12:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29 13:54 bug#32575: [Cuirass] Filter results by architecture Ricardo Wurmus
2018-08-29 20:49 ` Joshua Branson
2018-08-30  5:56   ` Gábor Boskovits
2018-08-30  8:09   ` Ricardo Wurmus
2018-08-30  9:41 ` Danny Milosavljevic
2018-08-30 12:14   ` Ludovic Courtès [this message]
2018-08-30 12:50     ` Clément Lassieur
2018-08-30 20:33       ` Ludovic Courtès
2018-08-31 18:35         ` Clément Lassieur
2021-03-25 13:32           ` Mathieu Othacehe

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=87efegxd9s.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=32575@debbugs.gnu.org \
    --cc=clement@lassieur.org \
    --cc=dannym@scratchpost.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).