CI reports "failed" even if build succeeds

  • Open
  • quality assurance status badge
Details
2 participants
  • Hartmut Goebel
  • Marius Bakke
Owner
unassigned
Submitted by
Hartmut Goebel
Severity
normal
H
H
Hartmut Goebel wrote on 3 Oct 2019 17:58
(name . bug-guix)(address . bug-guix@gnu.org)
45544e11-e094-4f29-81ce-4deb25707efe@crazy-compilers.com
Hi,

which i reported as "failed". But wen looking at the log-file, this
says: "@ build-succeeded
/gnu/store/a8hakfaf7a41ywxrssqlscqgcn642lhc-python-django-allauth-0.39.1.drv".

Maybe someone knowledgeable micht want to have a look.

--
Regards
Hartmut Goebel

| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
M
M
Marius Bakke wrote on 8 Oct 2019 21:40
877e5f58l7.fsf@devup.no
Hartmut Goebel <h.goebel@crazy-compilers.com> writes:

Toggle quote (7 lines)
> Hi,
>
> I just stepped over <https://ci.guix.gnu.org/build/1781422/details>,
> which i reported as "failed". But wen looking at the log-file, this
> says: "@ build-succeeded
> /gnu/store/a8hakfaf7a41ywxrssqlscqgcn642lhc-python-django-allauth-0.39.1.drv".

This happens when the failure was non-deterministic, and the build has
later been restarted somehow.

Fixing it seems difficult, since we don't want Cuirass to evaluate the
derivation on every request. Perhaps it could compare its own database
of failures with the daemon-cached failures?
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl2c5kQACgkQoqBt8qM6
VPowaAf/fbxLuM4lUGbstF8+FhGV9t7tnFYYEA5usknmYpIX25jrqxiODvBjwZ38
hgD4DK2lwHYSBgAzet4LyF1m5zMSF0nXCUKBlGgwJTdS1Y2wz3JfONZ4/Xu5wW8W
EI1aqcYPyYONdkbWTxTZ5Sh8JJ9NicyMDjXUMrUzzDiwnIfkApTZET8rz+ny8CJB
ER2jh9OKYOM8bM3jZsN5G4cWP1M9pZhmq6Z9Xg5+kBjh3E+eVieZEuj9x7JL7GEm
pmJ7llw0y+7+8PYxbfqGoZ0w+AGTEzhueI3r3BIVLDlOTXtTL4pS5yT5HohkVIGr
3iCedfSZYd0yI535CglsXTwzl1Q0ng==
=E57e
-----END PGP SIGNATURE-----

?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 37606@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 37606
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch