FTBFS on amd64 due to uninitialized values in unit-tests

Bug #1502907 reported by Łukasz Zemczak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-voice
Fix Released
Undecided
Łukasz Zemczak
unity-voice (Ubuntu)
Fix Released
Undecided
Łukasz Zemczak

Bug Description

The unity-voice fails in the wily test-rebuild [1] due to the unit tests failing:

1/1 Test #1: unit-tests .......................***Failed 1.74 sec
[==========] Running 4 tests from 1 test case.
[----------] Global test environment set-up.
[----------] 4 tests from TestPronounceDict
[ RUN ] TestPronounceDict.HashesInDictionary
==6554== Conditional jump or move depends on uninitialised value(s)
==6554== at 0x516ADDC: qDetectCpuFeatures() (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.4.2)
==6554== by 0x514487C: qHash(QString const&, unsigned int) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.4.2)
==6554== by 0x40D302: QHash<QString, QList<QString> >::findNode(QString const&, unsigned int*) const (qhash.h:912)
==6554== by 0x40CBB5: insert (qhash.h:768)
==6554== by 0x40CBB5: PronounceDict::loadDictionary(QString const&) (PronounceDict.cpp:96)
==6554== by 0x40A0E6: (anonymous namespace)::TestPronounceDict_HashesInDictionary_Test::TestBody() (TestPronounceDict.cpp:34)
==6554== by 0x42E182: HandleSehExceptionsInMethodIfSupported<testing::Test, void> (gtest.cc:2078)
==6554== by 0x42E182: void testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) (gtest.cc:2114)
==6554== by 0x4260EB: testing::Test::Run() [clone .part.373] (gtest.cc:2151)
==6554== by 0x4262C4: Run (gtest.cc:2142)
==6554== by 0x4262C4: testing::TestInfo::Run() [clone .part.374] (gtest.cc:2326)
==6554== by 0x426434: Run (gtest.cc:2301)
==6554== by 0x426434: testing::TestCase::Run() [clone .part.375] (gtest.cc:2444)
==6554== by 0x4268BC: Run (gtest.cc:4353)
==6554== by 0x4268BC: testing::internal::UnitTestImpl::RunAllTests() (gtest.cc:4315)
==6554== by 0x42E662: HandleSehExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool> (gtest.cc:2078)
==6554== by 0x42E662: bool testing::internal::HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool>(testing::internal::UnitTestImpl*, bool (testing::internal::UnitTestImpl::*)(), char const*) (gtest.cc:2114)
==6554== by 0x426BD4: testing::UnitTest::Run() (gtest.cc:3926)
(...)

[1] http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20151001-wily.html

Tags: ftbfs

Related branches

Changed in unity-voice (Ubuntu):
status: New → In Progress
description: updated
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Fix staged in a CI Train silo, will land later today.

Changed in unity-voice:
assignee: nobody → Łukasz Zemczak (sil2100)
status: New → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package unity-voice - 0.1+15.10.20151005-0ubuntu1

---------------
unity-voice (0.1+15.10.20151005-0ubuntu1) wily; urgency=medium

  [ Łukasz 'sil2100' Zemczak ]
  * Disable valgrind memcheck during testing as it's causing a test
    failure on amd64 (due to valgrind being angry at Qt internals).
    Remove the valgrind build-dependency. (LP: #1502907)

 -- Łukasz Zemczak <email address hidden> Mon, 05 Oct 2015 14:50:40 +0000

Changed in unity-voice (Ubuntu):
status: In Progress → Fix Released
Changed in unity-voice:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.