Bug#1057564: gnome-bluetooth3: FTBFS: failing tests

[Simon McVittie]

Control: unmerge 1057564 1058116
Control: reassign 1057564 python3-dbusmock 0.30.1-1
Control: retitle 1057564 python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS
Control: forwarded 1057564 https://github.com/martinpitt/python-dbusmock/issues/193
Control: affects 1057564 + src:gnome-bluetooth3
Control: reassign 1058116 gnome-bluetooth3 42.7-1
Control: retitle 1058116 gnome-bluetooth3: FTBFS: multiple tests time out with dbusmock >= 0.30.0
Control: forwarded 1058116 https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/142

On Sat, 30 Dec 2023 at 01:53:56 +0000, Simon McVittie wrote:
> On Tue, 05 Dec 2023 at 23:05:55 +0100, Santiago Vila wrote:
> > During a rebuild of all packages in unstable, your package failed to build:
> 
> This seems to be another casualty of recent updates to python-dbusmock.
> With python-dbusmock downgraded to 0.29.1-2, all tests pass and
> gnome-bluetooth3/42.7-1 builds successfully. With 0.30.0-2 (trixie)
> or 0.30.1-1 (sid), several tests time out.

I found a solution for the failure with dbusmock 0.30.0-2 and sent it
upstream to
https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/merge_requests/175, and
it works with dbusmock 0.30.0-2, but unfortunately one test still
fails with dbusmock 0.30.1-1. As far as I can see, that's genuinely a
dbusmock bug.

Because you can't clone a merged bug, I'm unmerging the two equivalent
FTBFS bug reports, and arbitrarily choosing to use:

- #1058116 to represent the gnome-bluetooth3 test failure with dbusmock
  0.30.0-2, which is genuinely a gnome-bluetooth3 bug, for which I've
  proposed a fix in
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/merge_requests/175.
  The symptom is that multiple tests time out.

- #1057564 to represent the gnome-bluetooth3 test failure with dbusmock
  0.30.1-1, even after applying GNOME/gnome-bluetooth!175, which as far
  as I can see is a dbusmock regression, reported as
  https://github.com/martinpitt/python-dbusmock/issues/193
  (I haven't tested a patch for this, I hope it's as simple as removing
  the obsolete 3rd argument in one call to PairDevice()).
  The symptom is that one test fails with
  "org.freedesktop.DBus.Error.InvalidArgs: Invalid arguments: Fewer
  items found in D-Bus signature than in Python arguments".

    smcv