Bug#953981: gcr: FTBFS (intermittently?): test_slot_info: assertion failed: (927623999 == token->utc_time)

Simon McVittie smcv at debian.org
Sun Mar 15 11:15:37 GMT 2020


Source: gcr
Version: 3.36.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=gcr&arch=armhf&ver=3.36.0-1&stamp=1583940931&raw=0
> 16/43 gcr:gck / slot                          FAIL     0.09 s (killed by signal 6 SIGABRT)
> 
> --- command ---
> 15:35:10 /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/gck/test-gck-slot
> --- stdout ---
> # random seed: R02S262f90c3cd5a7dc73705059898f1e9c5
> 1..7
> # Start of gck tests
> # Start of slot tests
> Bail out! Gck:ERROR:../gck/test-gck-slot.c:110:test_slot_info: assertion failed: (927623999 == token->utc_time)
> --- stderr ---
> **
> Gck:ERROR:../gck/test-gck-slot.c:110:test_slot_info: assertion failed: (927623999 == token->utc_time)
> -------

I rebuilt gcr locally (on amd64) and got the same test failure. It was
also seen on the i386, mipsel, alpha, hurd-i386, ia64, ppc64 and x32
autobuilders.

The amd64 autobuilder didn't get this (although there was a different
test failure) so presumably it's intermittent.

    smcv



More information about the pkg-gnome-maintainers mailing list