From: Leo Famulari <leo@famulari.name>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 46413@debbugs.gnu.org
Subject: bug#46413: tests/publish.scm fails on berlin
Date: Tue, 19 Jul 2022 09:52:25 -0400 [thread overview]
Message-ID: <Yta3GX6gEGmq9ijA@jasmine.lan> (raw)
In-Reply-To: <87sfn2uwpd.fsf@gmail.com>
On Fri, Jul 15, 2022 at 01:12:14PM -0400, Maxim Cournoyer wrote:
> Hi,
>
> Leo Famulari <leo@famulari.name> writes:
>
> > I notice that tests/publish.scm crashes consistently when run "by hand"
> > with `make check` on ci.guix.gnu.org:
> >
> > ------
> > $ make check -j1
> > [...]
> > PASS: tests/profiles.scm
> > make[4]: *** [Makefile:5520: tests/publish.log] Error 134
> > make[4]: Leaving directory '/home/lfam/guix'
> > make[3]: *** [Makefile:5502: check-TESTS] Error 2
> > make[3]: Leaving directory '/home/lfam/guix'
> > make[2]: *** [Makefile:5751: check-am] Error 2
> > make[2]: Leaving directory '/home/lfam/guix'
> > make[1]: *** [Makefile:5279: check-recursive] Error 1
> > make[1]: Leaving directory '/home/lfam/guix'
> > make: *** [Makefile:5753: check] Error 2
> > ------
> >
> > Since it crashes, the remainder of the tests are not run.
> >
> > I've attached the log, but I'm not sure what the problem is.
[...]
> I don't see any failure in the above test results?
The test suite crashes, so there are no error messages printed.
I haven't dug in, but I suspect the test suite doesn't handle the case
where the host machine is already running a `guix publish` server.
prev parent reply other threads:[~2022-07-19 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 23:20 bug#46413: tests/publish.scm fails on berlin Leo Famulari
2021-02-09 23:41 ` zimoun
2021-02-10 0:08 ` Leo Famulari
2021-02-10 1:45 ` zimoun
2021-12-28 22:35 ` Leo Famulari
2022-07-15 17:12 ` Maxim Cournoyer
2022-07-19 13:52 ` Leo Famulari [this message]
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=Yta3GX6gEGmq9ijA@jasmine.lan \
--to=leo@famulari.name \
--cc=46413@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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).