Public bug reported: gvfs's autopkgtests have begun failing in questing, sometime after September 14: https://autopkgtest.ubuntu.com/packages/gvfs/questing/amd64
migration-reference/0 runs will fail. I got qemu turned on for ci.debian.net today and the autopkgtests are passing there. Debian is using gvfs 1.58.0 instead of 1.57.2. https://ci.debian.net/packages/g/gvfs/unstable/amd64/ Historically, gvfs upstream did not run these tests. I don't know if that has changed. My guess was that the failure was triggered by the update of glib2.0 from 2.85.3-1 to 2.86.0-2. Debian still has glib 2.84 in Unstable so I triggered another test run with glib2.0 2.86.0-4 from experimental but it passed. 2.86.0-4 has some code changes compared to 2.86.0-2 but I didn't think they would affect this test. It looks like the logged syntax changed. *************** Failure excerpt *************** trash:// deletion for system location ... ok ====================================================================== drive mount: media player ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/gvfs-testbed-script", line 1272, in test_media_player self.assertRegex(out, 'Volume added:\s+.*bogus-cd') ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Regex didn't match: 'Volume added:\\s+.*bogus-cd' not found in "Volume changed: 'bogus-cd'\n Volume(0): bogus-cd\n … ** Affects: gvfs (Ubuntu) Importance: High Status: New ** Tags: questing update-excuse -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/2125781 Title: gvfs failing autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2125781/+subscriptions -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
