libqtdbustest fails to build against Qt 5.2 on x86
Bug #1262638 reported by
Timo Jyrinki
This bug report is a duplicate of:
Bug #1263926: libqtdbustest and libqtdbusmock fail to build on i386.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libqtdbustest |
Fix Committed
|
Critical
|
Pete Woods | ||
libqtdbustest (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Tests are failing:
This is one of the current blockers in getting the dependency chain rebuilt against Qt 5.2, see https:/
Related branches
lp:~pete-woods/libqtdbustest/valgrind-present-1263925
- Marcus Tomlinson (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
- Unity Team: Pending requested
-
Diff: 64 lines (+33/-2)3 files modifiedcmake/FindValgrind.cmake (+1/-1)
debian/control (+1/-1)
tests/data/valgrind.suppression (+31/-0)
Changed in libqtdbustest: | |
assignee: | nobody → Pete Woods (pete-woods) |
status: | New → In Progress |
To post a comment you must log in.
There are two things failing in here. Valgrind is detecting both:
1) An uninitialised value jump.
2) A variety of "possible" leaks inside Google Test
Each of these things seems to be out of my control. I think this is one of the few projects under CI that's running its tests under Valgrind. Anyway, the easy fix is to add some suppressions for the Google Test ones. They're probably false positives. However I think it's unlikely that these failures are caused by the new Qt version. More likely by something else, (new google test?).