It looks like the body of this autopkgtest was disabled in February as part of the fix for bug 1532358:
https://code.launchpad.net/~dobey/unity-scope-click/temp-no-int- tests/+merge/285079 All that remains is a package build triggered by "Restrictions: build- needed" in the debian/tests/control file. Does this really make sense? I thought autopkgtests were intended to test that the existing binary build still worked after its dependencies were updated. What this test is doing could just as easily give a false positive if a dependency changed in a source compatible but binary incompatible fashion. It also slows down landings of all its dependencies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610080 Title: unity-scope-click tests fail with segmentation fault in yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1610080/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
