Source: kpublictransport Followup-For: Bug #1113084 Control: severity -1 important Control: retitle -1 kpublictransport: sporadic test suite failure
Hi, the failure in the log file is the following: ********* Start testing of CacheTest ********* Config: Using QtTest library 6.8.2, Qt 6.8.2 (arm64-little_endian-lp64 shared (dynamic) release build; by GCC 14.3.0), debian unknown PASS : CacheTest::initTestCase() QWARN : CacheTest::testLocationCache() QIODevice::write (QFile, "/build/reproducible-path/kpublictransport-25.04.3/debian/.debhelper/generated/_source/home/.qttest/cache/org.kde.kpublictransport/backends/unittest/location/d5ad7d49e02f5cec70f1eab4288db4d936f3fa62.attribution"): device not open FAIL! : CacheTest::testLocationCache() Compared values are not the same Actual (entry.type) : 0 Expected (CacheHitType::Positive): 1 Loc: [./autotests/cachetest.cpp(58)] PASS : CacheTest::testLocationCacheKey() PASS : CacheTest::cleanupTestCase() Totals: 3 passed, 1 failed, 0 skipped, 0 blacklisted, 2ms ********* Finished testing of CacheTest ********* I tried to reproduce it with both - cmake 3.31.6 -- as currently available in unstable - cmake 4.1.2 -- as currently available in experimental and the build passed in both cases. My thought here is that the failure is simply a flakiness, possibly (but that's a very broad speculation though) due to the parallelism of the tests. Because of this, I'm - downgrading the severity to important - retitling accordingly, dropping the cmake 4 reference - dropping the cmake-4 user tagging If anyone has a reliable way to reproduce it, please do followup here so it can be properly investigated & fixed. Thanks, -- Pino
