all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: 65503@debbugs.gnu.org
Subject: bug#65503: Test suite logs aren't printed on failure during package build
Date: Thu, 24 Aug 2023 17:16:13 +0200	[thread overview]
Message-ID: <334ae96c-87d2-c938-a6b6-097ec6899172@telenet.be> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 1942 bytes --]

 From <https://ci.guix.gnu.org/build/1865837/log/raw>:

> make[4]: *** [Makefile:6303: tests/publish.log] Error 134
> make[4]: Leaving directory '/tmp/guix-build-guix-1.4.0-8.0e6215a.drv-0/source'
> make[3]: *** [Makefile:6285: check-TESTS] Error 2
> make[3]: Leaving directory '/tmp/guix-build-guix-1.4.0-8.0e6215a.drv-0/source'
> make[2]: *** [Makefile:6533: check-am] Error 2
> make[2]: Leaving directory '/tmp/guix-build-guix-1.4.0-8.0e6215a.drv-0/source'
> make[1]: *** [Makefile:6062: check-recursive] Error 1
> make[1]: Leaving directory '/tmp/guix-build-guix-1.4.0-8.0e6215a.drv-0/source'
> make: *** [Makefile:6535: check] Error 2
> 
> Test suite failed, dumping logs.
> error: in phase 'check': uncaught exception:
> %exception #<&invoke-error program: "make" arguments: ("check") exit-status: 2 term-signal: #f stop-signal: #f> 
> phase `check' failed after 358.4 seconds
> command "make" "check" failed with status 2
> builder for `/gnu/store/aw8li62xps10cz32crrxvm18ccafvzh0-guix-1.4.0-8.0e6215a.drv' failed with exit code 1
> @ build-failed /gnu/store/aw8li62xps10cz32crrxvm18ccafvzh0-guix-1.4.0-8.0e6215a.drv - 1 builder for `/gnu/store/aw8li62xps10cz32crrxvm18ccafvzh0-guix-1.4.0-8.0e6215a.drv' failed with exit code 1
> cannot build derivation `/gnu/store/dhf0chl41bj37a20c7bwdqnbjjgsc1i0-gwl-0.5.1.drv': 1 dependencies couldn't be built

Sure, the log has been dumped somewhere, but it's dumped in the build 
directory instead of the build log of the Guix package.  It would be 
quite convenient if there were some kind of flag or something (that is 
enabled in the package definition) to dump dump it to stderr.  Or just 
some ad-hoc:


(guard (c ((invoke-error? c)
            [copy all tests/*.log to stderr]
            (raise-continuable c)))
    [run tests]).

Alternatively, Cuirass could copy some parts of failed builds and 
present them in the UI.

Best regards,
Maxime Devos

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

             reply	other threads:[~2023-08-24 15:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24 15:16 Maxime Devos [this message]
2023-08-27  1:30 ` bug#65503: Test suite logs aren't printed on failure during package build Maxim Cournoyer

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=334ae96c-87d2-c938-a6b6-097ec6899172@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=65503@debbugs.gnu.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.