telepathy-qt's build tests are failing. This was hidden in the May
2026 upload because dh_auto_test wasn't being set with the correct
build directory for the dual qt5 & qt6 builds.

The build test failures are currently being ignored. If we aren't able
to fix the build test failures soon, it may be better to skip the
failing tests and stop ignoring the remaining test failures. This way
we can still detect when something breaks telepathy-qt.

Build log excerpt
=============
89% tests passed, 6 tests failed out of 55

Total Test time (real) =   1.58 sec

The following tests FAILED:
12 - DBusProperties (Failed)
13 - AccountBasics (Failed)
14 - AccountSet (Failed)
15 - AccountChannelDispatcher (Failed)
16 - Client (Failed)
48 - StreamTubeHandlers (Failed)

Additional build log excerpt
====================
48: QDEBUG : TestStreamTubeHandlers::initTestCase() tp-qt 0.9.8 DEBUG:
Calling Properties::GetAll(AccountManager)
48: QWARN  : TestStreamTubeHandlers::initTestCase() tp-qt 0.9.8 WARN:
GetAll(AccountManager) failed with
"org.freedesktop.DBus.Error.Spawn.ChildExited" : "Process
org.freedesktop.Telepathy.AccountManager exited with status 1"
48: QDEBUG : TestStreamTubeHandlers::initTestCase() tp-qt 0.9.8 DEBUG:
ReadinessHelper::setIntrospectCompleted: feature:
std::pair("Tp::AccountManager", 0) - success: false
48: QWARN  : TestStreamTubeHandlers::initTestCase()
"org.freedesktop.DBus.Error.Spawn.ChildExited": "Process
org.freedesktop.Telepathy.AccountManager exited with status 1"
48: FAIL!  : TestStreamTubeHandlers::initTestCase() Compared values
are not the same

Full build logs
==========
https://buildd.debian.org/status/package.php?p=telepathy-qt

Thank you,
Jeremy Bícha

fwiw, I don't see the test failures on my machine. The tests are known
to be racy, however, which is why the prior tp-qt maintainer disabled them.

For a start I'd suggest running the tests one at a time. Instead of
ARGS\+=-j16 in the override_dh_auto_test rule, use -j1. That might fix
some of them. On my machine sometimes the StreamTubeHandlers and
StatefulProxy tests completely deadlock trying to talk to dbus if I run
tests with -j16.

Even with -j1 though, I still sometimes see the occasional
StreamTubeHandlers failure.

For DBusProperties it's failing to create the AccountManager service;
I'm trying to figure out of that's at all related to a missing
build-dep. However, it'd be better to completely rule out problems due
to running multiple tests at once through a new upload.

Okay, figured it out. Need a build-dep (just for running tests) on
python3-gi. With that and -j1, I usually get 100% on tests.

We believe that the bug you reported is fixed in the latest version of
telepathy-qt, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1145519@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andres Salomon <dilinger@debian.org> (supplier of updated telepathy-qt package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Mon, 31 Aug 2026 22:53:26 -0400
Source: telepathy-qt
Architecture: source
Version: 0.9.8+git16.g04302908-5
Distribution: unstable
Urgency: medium
Maintainer: Debian UBports Team <team+ubports@tracker.debian.org>
Changed-By: Andres Salomon <dilinger@debian.org>
Closes: 1145519
Changes:
 telepathy-qt (0.9.8+git16.g04302908-5) unstable; urgency=medium
 .
   * Add build-dep on python3-gi to fix failing tests (closes: #1145519).
   * When running the build tests, run them one at a time; override
     debhelper's -j$(parallel) with a -j1.
Checksums-Sha1:
 5d0a73bd4154526080fa3c9953ee49225651dd6d 2853 telepathy-qt_0.9.8+git16.g04302908-5.dsc
 da6ee2d7ad15d8bfa41b50b4b85236baf9504aba 87016 telepathy-qt_0.9.8+git16.g04302908-5.debian.tar.xz
 d584c70264b8e322ff56f6e4c97aa39d34c102b8 17091 telepathy-qt_0.9.8+git16.g04302908-5_source.buildinfo
Checksums-Sha256:
 097cf88c71aa04987debbdb093b4749967193f75bb1aea8efb9ff5a2f46d847e 2853 telepathy-qt_0.9.8+git16.g04302908-5.dsc
 9d2ca8df3d0aa1c82d58df88a89ff477710972eea057c685af31cf9d024a211d 87016 telepathy-qt_0.9.8+git16.g04302908-5.debian.tar.xz
 cfbcf7c315a5d738251e1b26be14f3bafd315a9bb059813537f2513f5fa11bb2 17091 telepathy-qt_0.9.8+git16.g04302908-5_source.buildinfo
Files:
 2075375d391fc549fc07d2a017a4e1dd 2853 libs optional telepathy-qt_0.9.8+git16.g04302908-5.dsc
 d6769173e79891e798cc8354e381725d 87016 libs optional telepathy-qt_0.9.8+git16.g04302908-5.debian.tar.xz
 b75e47697c603223dfbafeadc8547083 17091 libs optional telepathy-qt_0.9.8+git16.g04302908-5_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQJIBAEBCAAyFiEEUAUk+X1YiTIjs19qZF0CR8NudjcFAmqWP00UHGRpbGluZ2Vy
QGRlYmlhbi5vcmcACgkQZF0CR8Nudjd1tA//fRPeCznOFVgYBO04R+bUBhuuxJd6
1tybpVrdcRjBRjE7KVT0n5m+PbXLcYlt5C1lG/316q201CWfAe2T685M9mIIaF2u
raCsR9lTLDz9F5cT3eEppshKcj53rEtgWH2e7mATFgMrmblVmhF8EvJZBdqrVTn7
efra95k16IKf4EI8JBnVn6wpehq+ryd0GvkvGQofHcaPDukwPy7hTxnOKJAWcVdR
CP1EOSOJm8IcX7F/TJ65B4dgAFkooFRLHtEGfsxJ3j31UpmtswO6wNhVrokHqEjF
TbxktcLZmZ7vyEwjFGYLUmQKcFanuMOmmdS1R44OmcvGK9bYESAANZVNccaLVxUS
gY2HyZR+NmOIq7BUorxqsLJMEi/Yps6RClInJ9bVXOLCNSfKt7NlzGqDEZkiAYYD
xRlfj7rvMU6iA6LArY3KlRE2cK4Zqd6MR/+epiJUTKI6iSXPCYaWeQWT5OxNpcT7
wWGM4aGmFnPC4FiBH5jmbLlScU1qFamvobwGPbIjQktaCnVZGkwG86HQbcpOoRM7
0pzgIM7I9++Y53bHZD9UHLNI8iPmh0xkJkhG4VtXy51AT+vISE73NtgK78+5wDfN
O19JqsPLsTt/CFMPNsNkY9ZsXv/paN9gDFbl6F9w5Mdrm2p6sNvjR+zIuCqgP950
YZSgZFuYs2we7SQ=
=somz
-----END PGP SIGNATURE-----

I'm reopening this bug because the current package in Debian Unstable
still has || true at the end of the dh_auto_test lines which means
that test failures are ignored. It looks like a few of the tests pass
sometimes but not reliably.

I think dh_auto_test should fail the build when build tests fail so in
Salsa, I removed || true

I had also removed your -j1 change because from what I can see,
parallel running doesn't increase the failure rate. However, I
restored dh_auto_test --no-parallel because you complained and because
it makes it easier to read the failing test logs.

I did notice that s390x appears to have at least one additional test
failure compared to other release architectures. I updated
debian/rules to ignore s390x build test failures since it is an
irrelevant architecture for Debian Lomiri's needs.

One workaround is to skip individual tests that aren't reliable.

Thank you,
Jeremy Bícha

That's fine (and known). I think the way to do this for now would be to
fail if there's more than 1 test failure. Otherwise, assume there will
likely be a race-related test failure somewhere. I've seen other
packages do this (I'm thinking llvm or rust, I forget which one). That's
assuming we can't narrow down the specific racy tests to disable, but I
think we'll need more package uploads before we spot the pattern.

Long-term we'd obviously like to actually fix the races, but I'm still
waiting for upstream to even look at my Qt6 and deprecated-warning-fixes
merge requests.

What I see on my end is that 2 tests in particular will conflict with
each other and cause the entire test process to deadlock and hang until
it finally times out*. Not a great thing to happen on a buildd, and also
super annoying locally when kicking off a build, switching to another
workspace, and coming back to it a few minutes later expecting packages
but instead finding a hung process.

  * as a side note, the test timeout limit should probably be shortened
to make this less painful when it happens.