From: ludo@gnu.org (Ludovic Courtès)
To: 18445@debbugs.gnu.org
Subject: bug#18445: glib failing to build
Date: Thu, 04 Dec 2014 14:01:08 +0100 [thread overview]
Message-ID: <8761dr4lij.fsf@gnu.org> (raw)
In-Reply-To: <87wq69902z.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 02 Dec 2014 23:08:20 +0100")
ludo@gnu.org (Ludovic Courtès) skribis:
> I built it locally and got another error:
>
> PASS: gapplication 1 /gapplication/no-dbus
> PASS: gapplication 2 /gapplication/no-appid
> PASS: gapplication 3 /gapplication/properties
> PASS: gapplication 4 /gapplication/app-id
> ERROR: gapplication - missing test plan
> ERROR: gapplication - exited with status 134 (terminated by signal 6?)
>
> where gapplication.log reads this:
>
> # random seed: R02S5b9338846cb34d3593b1becfb1a22081
> # Start of gapplication tests
> ok 1 /gapplication/no-dbus
> PASS: gapplication 1 /gapplication/no-dbus
> ok 2 /gapplication/no-appid
> PASS: gapplication 2 /gapplication/no-appid
> ok 3 /gapplication/properties
> PASS: gapplication 3 /gapplication/properties
> Failed to register: The connection is closed
> **
> GLib-GIO:ERROR:gapplication.c:564:test_quit: assertion failed: (activated)
> ok 4 /gapplication/app-id
Commit 36d2a3a disables this particular test, and Hydra successfully
built GLib.
I found another report suggesting that this test is unreliable, FWIW:
<https://bugs.debian.org/756273>.
Ludo’.
next prev parent reply other threads:[~2014-12-04 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 15:30 bug#18445: glib failing to build lemonnierk
2014-09-22 8:38 ` Ludovic Courtès
2014-12-02 22:08 ` Ludovic Courtès
2014-12-04 13:01 ` Ludovic Courtès [this message]
2015-04-06 20:09 ` Ludovic Courtès
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=8761dr4lij.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=18445@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.