← Back to team overview

touch-packages team mailing list archive

[Bug 1422578] [NEW] segfault in QSearchQueryBase test

 

Public bug reported:

Just got this on Jenkins CI for arm:

The following tests FAILED:
	 82 - QSearchQueryBaseAPI (SEGFAULT)

That's from the output at the end of the console log.

The actual test run output is:

test 82
        Start  82: QSearchQueryBaseAPI

82: Test command: /tmp/buildd/unity-scopes-api-0.6.14+15.04.20150213bzr316pkg0vivid102/obj-arm-linux-gnueabihf/test/gtest/scopes/qt/qt-bindings/QSearchQueryBaseAPI_test
82: Test timeout computed to be: 1500
82: Running main() from gmock_main.cc
82: [==========] Running 1 test from 1 test case.
82: [----------] Global test environment set-up.
82: [----------] 1 test from TestSetup
82: [ RUN      ] TestSetup.bindings
82: SetUp()
82: Starting qt application
82: Thread id is: 0xb3a3b320
82: 
82: GMOCK WARNING:
82: Uninteresting mock function call - returning default value.
82:     Function call: event(0x803668)
82:           Returns: false
82: Stack trace:
 82/102 Test  #82: QSearchQueryBaseAPI .................................***Exception: SegFault  0.60 sec
Running main() from gmock_main.cc
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from TestSetup
[ RUN      ] TestSetup.bindings
SetUp()
Starting qt application
Thread id is: 0xb3a3b320

GMOCK WARNING:
Uninteresting mock function call - returning default value.
    Function call: event(0x803668)
          Returns: false
Stack trace:

** Affects: unity-scopes-api (Ubuntu)
     Importance: High
     Assignee: Michi Henning (michihenning)
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1422578

Title:
  segfault in QSearchQueryBase test

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Just got this on Jenkins CI for arm:

  The following tests FAILED:
  	 82 - QSearchQueryBaseAPI (SEGFAULT)

  That's from the output at the end of the console log.

  The actual test run output is:

  test 82
          Start  82: QSearchQueryBaseAPI

  82: Test command: /tmp/buildd/unity-scopes-api-0.6.14+15.04.20150213bzr316pkg0vivid102/obj-arm-linux-gnueabihf/test/gtest/scopes/qt/qt-bindings/QSearchQueryBaseAPI_test
  82: Test timeout computed to be: 1500
  82: Running main() from gmock_main.cc
  82: [==========] Running 1 test from 1 test case.
  82: [----------] Global test environment set-up.
  82: [----------] 1 test from TestSetup
  82: [ RUN      ] TestSetup.bindings
  82: SetUp()
  82: Starting qt application
  82: Thread id is: 0xb3a3b320
  82: 
  82: GMOCK WARNING:
  82: Uninteresting mock function call - returning default value.
  82:     Function call: event(0x803668)
  82:           Returns: false
  82: Stack trace:
   82/102 Test  #82: QSearchQueryBaseAPI .................................***Exception: SegFault  0.60 sec
  Running main() from gmock_main.cc
  [==========] Running 1 test from 1 test case.
  [----------] Global test environment set-up.
  [----------] 1 test from TestSetup
  [ RUN      ] TestSetup.bindings
  SetUp()
  Starting qt application
  Thread id is: 0xb3a3b320

  GMOCK WARNING:
  Uninteresting mock function call - returning default value.
      Function call: event(0x803668)
            Returns: false
  Stack trace:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1422578/+subscriptions


Follow ups

References