[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#839134: qbs: FTBFS on sparc64: Testsuite failures



Source: qbs
Version: 1.6.0+dfsg-2
Severity: normal
User: debian-sparc@lists.debian.org
Usertags: sparc64

Hi!

qbs currently fails to build from source on sparc64 due to quite a number
of tests failing:

********* Start testing of qbs::Internal::TestBuildGraph *********
Config: Using QtTest library 5.6.1, Qt 5.6.1 (sparcv9-big_endian-lp64 shared (dynamic) release build; by GCC 6.1.1 20160724)
********* Start testing of qbs::Internal::TestLanguage *********
Config: Using QtTest library 5.6.1, Qt 5.6.1 (sparcv9-big_endian-lp64 shared (dynamic) release build; by GCC 6.1.1 20160724)
PASS   : qbs::Internal::TestBuildGraph::initTestCase()
PASS   : qbs::Internal::TestBuildGraph::testCycle()
PASS   : qbs::Internal::TestBuildGraph::cleanupTestCase()
Totals: 3 passed, 0 failed, 0 skipped, 0 blacklisted
********* Finished testing of qbs::Internal::TestBuildGraph *********
make[5]: Leaving directory '/<<BUILDDIR>>/qbs-1.6.0+dfsg/tests/auto/buildgraph'
QDEBUG : qbs::Internal::TestLanguage::initTestCase() SOFT ASSERT: m_definePropertyFunction.isFunction() in language/scriptengine.cpp:91
QDEBUG : qbs::Internal::TestLanguage::initTestCase() SOFT ASSERT: m_emptyFunction.isFunction() in language/scriptengine.cpp:93
QDEBUG : qbs::Internal::TestLanguage::initTestCase() SOFT ASSERT: m_proto.isObject() in language/scriptengine.cpp:436
QDEBUG : qbs::Internal::TestLanguage::initTestCase() SOFT ASSERT: f.isFunction() in language/scriptengine.cpp:443
QDEBUG : qbs::Internal::TestLanguage::initTestCase() SOFT ASSERT: f.isFunction() in language/scriptengine.cpp:443
QDEBUG : qbs::Internal::TestLanguage::initTestCase() SOFT ASSERT: f.isFunction() in language/scriptengine.cpp:443
QDEBUG : qbs::Internal::TestLanguage::initTestCase() SOFT ASSERT: f.isFunction() in language/scriptengine.cpp:443
QDEBUG : qbs::Internal::TestLanguage::initTestCase() SOFT ASSERT: m_proto.isObject() in language/scriptengine.cpp:436
QDEBUG : qbs::Internal::TestLanguage::initTestCase() SOFT ASSERT: f.isFunction() in language/scriptengine.cpp:443
QDEBUG : qbs::Internal::TestLanguage::initTestCase() SOFT ASSERT: f.isFunction() in language/scriptengine.cpp:443
QDEBUG : qbs::Internal::TestLanguage::initTestCase() SOFT ASSERT: f.isFunction() in language/scriptengine.cpp:443
PASS   : qbs::Internal::TestLanguage::initTestCase()
QDEBUG : qbs::Internal::TestLanguage::baseProperty() SOFT ASSERT: !observer || !m_propertyObserver in language/item.cpp:175
QDEBUG : qbs::Internal::TestLanguage::baseProperty() SOFT ASSERT: !observer || !m_propertyObserver in language/item.cpp:175
QDEBUG : qbs::Internal::TestLanguage::baseProperty() SOFT ASSERT: !observer || !m_propertyObserver in language/item.cpp:175
QDEBUG : qbs::Internal::TestLanguage::baseProperty() SOFT ASSERT: !observer || !m_propertyObserver in language/item.cpp:175
QDEBUG : qbs::Internal::TestLanguage::baseProperty() "/<<BUILDDIR>>/qbs-1.6.0+dfsg/src/lib/corelib/language/testdata/baseproperty_base.qbs The 'profiles' property cannot be an empty list."
FAIL!  : qbs::Internal::TestLanguage::baseProperty() Compared values are not the same
   Actual   (exceptionCaught): 1
   Expected (false)          : 0
   Loc: [language/tst_language.cpp(181)]
QDEBUG : qbs::Internal::TestLanguage::buildConfigStringListSyntax() SOFT ASSERT: !observer || !m_propertyObserver in language/item.cpp:175
(...)
FAIL!  : TestBlackbox::zip(jar) Compared values are not the same
   Actual   (status): 1
   Expected (0)     : 0
   Loc: [tst_blackbox.cpp(400)]
FAIL!  : TestBlackbox::zipInvalid() 'm_qbsStderr.contains("unrecognized archive tool: 'something'")' returned FALSE. (ERROR: Profile "qbs_autotests" has a non-existent base profile "nan".
)
   Loc: [tst_blackbox.cpp(444)]
PASS   : TestBlackbox::cleanupTestCase()
Totals: 6 passed, 124 failed, 47 skipped, 0 blacklisted
********* Finished testing of TestBlackbox *********

Due to the high number of tests failing - 124 to be exact - I assume there is some fundamental
problem with qbs on sparc64 which affects most of the tests. If someone has a clue where to
start looking, the sparc64 porters would be happy to know and happy to help!

We are aiming to turn sparc64 into a release architecture in the near future. Hence it is
necessary to sort issues like these out.

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


Reply to: