tracker 3.7.1 failing tracker:core / service test
Debian and Ubuntu's autopkgtest system is detecting a new test failure in tracker 3.7.1 compared to 3.7.0
Excerpt
77s ==============================================================================
77s
77s =================================== 31/32 ====================================
77s test: tracker:core / service
77s start time: 14:11:59
77s duration: 3.64s
77s result: killed by signal 6 SIGABRT
77s command: LANGUAGE=en_US:C:POSIX LANG=en_US.UTF8 TRACKER_DEBUG=fts-integrity MALLOC_PERTURB_=144
LD_LIBRARY_PATH=/tmp/autopkgtest-lxc.lhm6of2s/downtmp/build.9H3/src/obj-x86_64-linux-gnu/src/libtracker-sparql
/tmp/autopkgtest-lxc.lhm6of2s/downtmp/build.9H3/src/obj-x86_64-linux-gnu/tests/core/tracker-service-test
…
77s not ok /core/dbus/service/service-nonexistent-3 - Tracker:ERROR:
../src/libtracker-sparql/remote/tracker-http.c:112:ensure_types: code should not be reached
77s Bail out!
77s ----------------------------------- stderr -----------------------------------
77s **
77s Tracker:ERROR:../src/libtracker-sparql/remote/tracker-http.c:112:ensure_types: code should not be reached
Full logs
Click the download button next to test log at https://ci.debian.net/packages/t/tracker/testing/amd64/
Ubuntu's autopkgtests are a little messier with how Ubunt https://autopkgtest.ubuntu.com/packages/tracker/noble/amd64
Configuration
https://salsa.debian.org/gnome-team/tracker/-/blob/debian/latest/debian/tests/unit-tests
which is similar but not identical to https://salsa.debian.org/gnome-team/tracker/-/blob/debian/latest/debian/rules
which does pass