On Fri, Feb 17, 2017 at 08:54:54AM -0600, Jeff Epler wrote: > On Fri, Feb 17, 2017 at 12:16:16PM +0100, Santiago Vila wrote: > > Can anyone here reproduce any of the following *two* bugs? > > (Using sbuild in a single-CPU machine) > > 837067 1.000 libsecret > > Using a fresh 1CPU / 1GB x86 system on digitalocean's NYC region, upgraded to > debian testing, I tried sbuilding libsecret. So far, 2/2 builds failed. https://tests.reproducible-builds.org/libsecret looks better: - 7x success - 1x ftbfs (actually, that's 13 successful builds and one failure, as we always build twice…) https://tests.reproducible-builds.org/debian/logs/testing/armhf/libsecret_0.18.5-2.build2.log.gz failed with: FAIL: test-session 4 /session/ensure-async-aes ** ERROR:libsecret/test-session.c:167:test_ensure_async_aes: assertion failed: (G_IS_ASYNC_RESULT (result)) (These systems have more cores and more memory too, but also do several builds at the same time…) -- cheers, Holger
Attachment:
signature.asc
Description: Digital signature