unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
* bug#33310: Cuirass: Evaluations adding no new builds are displayed as "failing"
@ 2018-11-08  9:34 Clément Lassieur
  2018-11-11 13:37 ` Ludovic Courtès
  0 siblings, 1 reply; 3+ messages in thread
From: Clément Lassieur @ 2018-11-08  9:34 UTC (permalink / raw)
  To: 33310

Hi,

Evaluations adding no new builds are displayed as "failing".  I know
this was done on purpose, but I think the check should be done on the
number of jobs returned by the evaluator, rather than on the number of
builds registered in the database.

There is a difference because derivations that are already in the
database won't be added again.

In my case (https://cuirass.lassieur.org/jobset/guix-manifest-clem), 70%
of the evaluations add no new builds, and none of them are failing.

--8<---------------cut here---------------start------------->8---
    (with-store store
      (let ((jobs (evaluate store spec eval-id checkouts)))
        (log-message "building ~a jobs for '~a'"
                     (length jobs) name)
        (build-packages store jobs eval-id)))
--8<---------------cut here---------------end--------------->8---

Thus if (zero? (length jobs)) here, we should mark the corresponding
evaluation as failing.

Thanks,
Clément

^ permalink raw reply	[flat|nested] 3+ messages in thread

* bug#33310: Cuirass: Evaluations adding no new builds are displayed as "failing"
  2018-11-08  9:34 bug#33310: Cuirass: Evaluations adding no new builds are displayed as "failing" Clément Lassieur
@ 2018-11-11 13:37 ` Ludovic Courtès
  2021-03-25 12:54   ` Mathieu Othacehe
  0 siblings, 1 reply; 3+ messages in thread
From: Ludovic Courtès @ 2018-11-11 13:37 UTC (permalink / raw)
  To: Clément Lassieur; +Cc: 33310

Hello,

Clément Lassieur <clement@lassieur.org> skribis:

> Evaluations adding no new builds are displayed as "failing".  I know
> this was done on purpose, but I think the check should be done on the
> number of jobs returned by the evaluator, rather than on the number of
> builds registered in the database.

Indeed, that makes sense.  For the record the faulty code was added in
commit 0b40dca734468e8b12b3ff58e3e779679f17d38e.  As I wrote there, it
would be ideal to have a “failed” bit in the database, and, even better,
to save the output of ‘evaluate’.

Thanks,
Ludo’.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* bug#33310: Cuirass: Evaluations adding no new builds are displayed as "failing"
  2018-11-11 13:37 ` Ludovic Courtès
@ 2021-03-25 12:54   ` Mathieu Othacehe
  0 siblings, 0 replies; 3+ messages in thread
From: Mathieu Othacehe @ 2021-03-25 12:54 UTC (permalink / raw)
  To: 33310-done


Hello,

Closing as this is fixed on Cuirass master.

Thanks,

Mathieu




^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-03-25 12:55 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-11-08  9:34 bug#33310: Cuirass: Evaluations adding no new builds are displayed as "failing" Clément Lassieur
2018-11-11 13:37 ` Ludovic Courtès
2021-03-25 12:54   ` Mathieu Othacehe

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).