qmluitests cause a segfault which is then ignored

[Christopher Lee]

There are a number of UNSTABLE failures in the unity-phablet-qmluitests-trusty jenkins job is due to the testDashContents tests causing a segfault.
(You can see this by checking out the console log and searching for 'segmentation fault' i.e. https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-trusty/336/consoleText)

The segfault means that the newly created testDashContent.xml file is never populated with details. The jenkins job then sees this 0-length file and considers it indicative of a failed test and marks the job as UNSTABLE.

I guess this might be 2 bugs:

  - The runtests.sh script doesn't return failure if this happens
  - The tests cause a segfault (I'm pretty sure the segfault is happening in qmltestrunner, in the process of getting further details).

[Michał Sawicz (saviq)]

This segfault is most likely happening in unity8 as well, I'm suspecting this to be a duplicate of bug #1240408 - not easily reproducible as of yet, unfortunately.

[Christopher Lee (veebers)]

Nice catch , thanks for picking up on that so quickly.

It does show an issue with the test runner thought that if there is a segfault or similar error it's not considered a failure or report as such (not easily to see at least).
I'll look into this aspect of it a little further.

[kevin gunn (kgunn72)]

chris gonna check on duplicity...marking incomplete for now

[Launchpad Janitor (janitor)]

[Expired for Unity 8 because there has been no activity for 60 days.]