ubuntu-sdk-bugs team mailing list archive

[Launchpad Bug Tracker <1567286@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package ubuntu-ui-toolkit -
1.3.1984+16.10.20160527.2

---------------
ubuntu-ui-toolkit (1.3.1984+16.10.20160527.2) yakkety; urgency=medium

  [ Christian Dywan ]
  * Slimmer frame for TextFields: 0.5dp. Fixes LP: #1578190.

  [ Albert Astals Cid ]
  * Add override
    The override specifier (since C++11) specifies that a virtual function
    overrides another virtual function. In a member function declaration or
    definition, override ensures that the function is virtual and is overriding
    a virtual function from the base class.

  [ Tim Peeters ]
  * Fix reference error in PullToRefreshStyle. Fixes LP: #1582843
  * Mark Tab, Tabs, TabBar, PageHeadConfiguration, PageHeadSections,
    PageHeadState, ToolbarButton, ToolbarItems as deprecated in the
    documentation. Fixes LP: #1566735, LP: #1566741.

  [ CI Train Bot ]
  * Resync trunk.

 -- Zoltan Balogh <zoltan.balogh@xxxxxxxxxxxxx>  Fri, 27 May 2016
07:08:44 +0000

** Changed in: ubuntu-ui-toolkit (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to ubuntu-ui-toolkit in Ubuntu.
https://bugs.launchpad.net/bugs/1567286

Title:
  Test runner script gives PASS on segmentation faults

Status in Canonical System Image:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  Fix Released

Bug description:
  r1920

  Today I mistakingly pushed a new unit test in an MR without "bzr
  add"ing the corresponding QML file.

  CI didn't say anything about it, tests were "PASS" on all architectures, the MR was approved, and it was about to land.  Later in the day I realized I had not pushed the QML file.
  But still, I got all PASS when I should have clearly got FAIL.

  So I manually checked the (PASSing) console log from Jenkins, and found:
  - a QWARN in the test saying that it couldn't find the QML file
  - a segfault in the same test, due to the previous point

  The UITK test suite has a script that runs the tests and checks,
  beside other things, that there were no QWARN issues by tests. That
  check is done by parsing a per-test result .xml that is written at the
  end of each test.

  I think what is happening in this case is that the .xml file is not
  being created at all because of the segfault, and the test runner is
  not detecting that.

  So, potentially, there are other segfaults in other test results that
  have never been caught so far, and could uncover new test failures :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567286/+subscriptions