On Fri, 31 May 2024 08:51:58 +0200 Paul Gevers <elb...@debian.org> wrote: > Hi, > > On Wed, 15 May 2024 10:16:55 +0200 Emilio Pozuelo Monfort > <po...@debian.org> wrote: > > If this can't be fixed in the > > short term by adding some type of restriction to the autopkgtest > > or by mocking the devices, then the tests should be removed until > > they can be made to work on our infrastructure. > > The autopkgtest failure is not due to the test failing itself, but due=20 > to the test writing to stderr, which by default is considered a test > failure. You can ignore output to stderr by marking the test with the > allow-stderr restriction. But please, if you do that, this test doesn't=20 > actually do anything anymore on Debian infrastructure so be sure to also=20 > mark it as superficial or mark the test as skippable and exit with exit=20 > code 77 in case all tests are skipped. > > Paul
Please could you push a fix to the test so that bluez can migrate to Debian testing? Newer versions has fixed some bugs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060795 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060393 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060242 Best, Amr
