Ubuntu
unity8 package

unity8 fails to build in arm64 because of tests segfault

Bug #1641175 reported by Marco Trevisan (Treviño)
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntu-system-settings (Ubuntu)
Confirmed
Critical
Unassigned
unity8 (Ubuntu)
Confirmed
Critical
Unassigned

Bug Description

Recent builds of unity8 fails in arm64 because of this error

See for example: https://launchpadlibrarian.net/293000651/buildlog_ubuntu-zesty-arm64.unity8_8.15+17.04.20161111.1-0ubuntu1_BUILDING.txt.gz

21/23 Test #18: testUtilsStyle ...................***Exception: SegFault 0.43 sec

https://launchpadlibrarian.net/292999853/buildlog_ubuntu-xenial-arm64.ubuntu-system-settings_0.4+16.04.20161111-0ubuntu1_BUILDING.txt.gz

29/29 Test #29: tst_notifications ...................***Failed 0.62 sec
Segmentation fault (core dumped)

(gdb) ========= End of stack trace ==============
QFATAL : TrustStoreModelTest::testEmpty() Received signal 11
         Function time: 6ms Total time: 7ms
FAIL! : TrustStoreModelTest::testEmpty() Received a fatal error.
   Loc: [Unknown file(0)]
Totals: 1 passed, 1 failed, 0 skipped, 0 blacklisted
********* Finished testing of TrustStoreModelTest *********
Aborted (core dumped)

See original description
Marco Trevisan (Treviño) (3v1n0)
summary: - unity8 fails to build in arm64 because of pragma Singleton
+ unity8 fails to build in arm64 because of tests segfault
description: updated
Changed in ubuntu-system-settings (Ubuntu):
status: New → Triaged
importance: Undecided → Critical
description: updated
Revision history for this message
Marco Trevisan (Treviño) (3v1n0) wrote :

It was probably something temporary... It works now.

Changed in ubuntu-system-settings (Ubuntu):
status: Triaged → Fix Released
Changed in unity8 (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Michał Sawicz (saviq) wrote :

Well, we still need to look at it and at least try and reproduce ;)

Changed in unity8 (Ubuntu):
status: Fix Released → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity8 (Ubuntu):
status: New → Confirmed
Revision history for this message
Jonas G. Drange (jonas-drange) wrote :

Yeah, seeing this in USS builds as well [1].

[1] https://launchpadlibrarian.net/292919062/buildlog_ubuntu-zesty-arm64.ubuntu-system-settings_0.4+17.04.20161110.2-0ubuntu1_BUILDING.txt.gz

Changed in ubuntu-system-settings (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Albert Astals Cid (aacid) wrote :

Isn't this the "Qt doesn't like the new arm64 kernel" bug we already had that made us revert the kernel?

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

The general problem is that the new kernel comes back at each upgrade of the ubuntu kernel, and a custom one needs installation for each. But yes bug #1630906 is still open.

Qt 5.7.1 and 5.6.3 (in March or so) will eventually have upstream fixes that hopefully work fully unlike the cherry-picks that had their own issues in my testing.

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.