Efraim Flashner <efr...@flashner.co.il> writes:

> [...]
>
> I just applied the first three patches and glib failed to build, with
> the following errors from the test phase:
>
> ERROR: gapplication - too few tests run (expected 12, got 4)
> ERROR: gapplication - exited with status 139 (terminated by signal 11?)
>
> Unfortunately I didn't tell it to keep the output of the build so I
> can't attach the test-suite.log file. It would be best if glib built
> with this commit, just in case.

So these tests are really unreliable...  
I did get it build sucessful with the patch on my x86-64 machine,
and this patch doesn't enable the '/gapplication/quit' test (it pass
too on my machine).

Could you build it with '-K', show the log (not very useful, IMO), and
the run the test manually in a container environment by:
--8<---------------cut here---------------start------------->8---
$ guix environment -C --pure glib
# cd gio/tests
# ./gapplication
--8<---------------cut here---------------end--------------->8---

Also, one can skip some test cases using something like:
--8<---------------cut here---------------start------------->8---
./gapplication -s '/gapplication/quit' -s '/gapplication-remote-actions'
--8<---------------cut here---------------end--------------->8---
I use this to filter out mis-disabled test cases in the origin patches.

Thanks!

Reply via email to