Ubuntu
unity-scope-click package

unity-scope-click tests fail with segmentation fault in yakkety

Bug #1610080 reported by Timo Jyrinki
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-scope-click (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

This new (brought to you by GCC6) failure prevents Qt, KDE etc from migrating from proposed to relese pocket in yakkety.

--
[ RUN ] DepartmentsTest.testRootDepartment
SCHEMA dir: /tmp/autopkgtest.ybKROD/build.1Zh/unity-scope-click-0.1.1+16.10.20160705/obj-x86_64-linux-gnu/scope/tests
Segmentation fault (core dumped)
scope/tests/CMakeFiles/test-apps-scope.dir/build.make:60: recipe for target 'scope/tests/CMakeFiles/test-apps-scope' failed
make[4]: *** [scope/tests/CMakeFiles/test-apps-scope] Error 139
--

Revision history for this message
James Henstridge (jamesh) wrote :

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.

Revision history for this message
dobey (dobey) wrote :

This was fixed by a no-change rebuild that doko uploaded to yakkety, for the boost ABI breakage.

Changed in unity-scope-click (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.