Your message dated Tue, 29 Aug 2017 18:53:23 +0300
with message-id <20170829155323.zumev64sfxnoetzw@localhost>
and subject line Re: Bug#870312: flatpak FTBFS on amd64/arm64: ERROR:
testlibrary - missing test plan
has caused the Debian Bug report #870312,
regarding flatpak FTBFS on amd64/arm64: ERROR: testlibrary - missing test plan
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
870312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flatpak
Version: 0.8.7-4
Severity: serious
Some recent change in unstable makes flatpak FTBFS on amd64/arm64:
https://tests.reproducible-builds.org/debian/history/flatpak.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/flatpak.html
...
ERROR: testlibrary - missing test plan
ERROR: testlibrary - exited with status 134 (terminated by signal 6?)
=====================================
Flatpak 0.8.7: ./test-suite.log
=====================================
# TOTAL: 20
# PASS: 6
# SKIP: 12
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 2
.. contents:: :depth: 2
SKIP: test-doc-portal
=====================
# random seed: R02S2d187e435d4aa4fb68938109e0122c30
1..2
# Start of db tests
ok 1 /db/create_doc # SKIP this test requires FUSE
SKIP: test-doc-portal 1 /db/create_doc # SKIP this test requires FUSE
ok 2 /db/recursive_doc # SKIP this test requires FUSE
SKIP: test-doc-portal 2 /db/recursive_doc # SKIP this test requires FUSE
# End of db tests
ERROR: testlibrary
==================
**
flatpak:ERROR:tests/testlibrary.c:668:add_remote: assertion failed (status ==
0): (256 == 0)
./buildutil/tap-test: line 23: 59830 Aborted ${srcd}/${bn} -k
--tap
# random seed: R02Sbf4ab0218f9346d8617da03c0d7234c9
# flatpak:ERROR:tests/testlibrary.c:668:add_remote: assertion failed (status ==
0): (256 == 0)
ERROR: testlibrary - missing test plan
ERROR: testlibrary - exited with status 134 (terminated by signal 6?)
...
--- End Message ---
--- Begin Message ---
Version: 0.9.7-1
On Tue, Aug 29, 2017 at 03:05:34PM +0100, Simon McVittie wrote:
> On Tue, 01 Aug 2017 at 00:38:58 +0300, Adrian Bunk wrote:
> > Some recent change in unstable makes flatpak FTBFS on amd64/arm64:
> >
> > https://tests.reproducible-builds.org/debian/history/flatpak.html
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/flatpak.html
>
> I can't reproduce this in my local sbuild, but it's still happening on
> the reproducible-builds infrastructure. It might be related to the use
> of pbuilder on reproducible-builds?
>
> Have you reproduced this yourself, or are you reporting it purely based on
> what you see on reproducible-builds.org?
I actually tried a rebuild in a chroot before reporting in this case,
but that failed even earlier:
flatpak:ERROR:tests/testlibrary.c:550:make_test_runtime: assertion failed
(status == 0): (256 == 0)
> > # random seed: R02Sbf4ab0218f9346d8617da03c0d7234c9
> > # flatpak:ERROR:tests/testlibrary.c:668:add_remote: assertion failed
> > (status == 0): (256 == 0)
>
> This is status from:
>
> g_spawn_sync (NULL, (char **)argv, NULL, flags, NULL, NULL, NULL, NULL,
> &status, &error);
>
> where argv is { "flatpak", "remote-add", ... } and error indicates that
> g_spawn_sync() did not immediately fail (therefore status is a waitpid()
> result). Applying WIFEXITED() and WEXISTATUS() indicates that
> "flatpak remote-add ..." exited 1.
>
> The next step is to make this fail in an environment where g_test_verbose()
> would return true (or patch out that check), so that we see flatpak's stderr.
> I'm not entirely sure why upstream suppressed its stderr here.
The version in experimental is fine, so there's not much point in
spending time debugging here.
I actually wonder why I didn't close it with that version when reporting,
doing it now.
Technically this will still be an RC bug in flatpak in unstable,
but since flatpak is a key package it won't trigger autoremoval
and everything will be fine once flatpak 0.9/1.0 enters unstable.
> S
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--- End Message ---
