[okteta] [Bug 467541] 0.26.10: Test suite is failing
https://bugs.kde.org/show_bug.cgi?id=467541 Friedrich W. H. Kossebau changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED Latest Commit||https://invent.kde.org/util ||ities/okteta/commit/f8ea84b ||e37fa5440cb3a2c61858efe520f ||957cc2 Version Fixed In||0.26.11 --- Comment #7 from Friedrich W. H. Kossebau --- Git commit f8ea84be37fa5440cb3a2c61858efe520f957cc2 by Friedrich W. H. Kossebau. Committed on 04/05/2023 at 14:04. Pushed by kossebau into branch '0.26'. Fix accidentally shared unit test working directories Runs risk in parallel test runs to have the dirs cleaned up while being used by a parallel test. FIXED-IN: 0.26.11 M +1-1kasten/core/io/tests/bytearrayrawfilesynchronizerfactorytest.cpp M +1-1 libs/kasten/core/tests/testdocumentfilesynchronizerfactorytest.cpp https://invent.kde.org/utilities/okteta/commit/f8ea84be37fa5440cb3a2c61858efe520f957cc2 -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 467541] 0.26.10: Test suite is failing
https://bugs.kde.org/show_bug.cgi?id=467541 kloczek changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #6 from kloczek --- What kind of informations do you need? Just retested this issue on top of latest KDE packages and qt 5.15.8 and those units are still failing + cd okteta-0.26.10 + xvfb-run -a /usr/bin/ctest --test-dir x86_64-redhat-linux-gnu --output-on-failure --force-new-ctest-process -j48 ' ' Internal ctest changing into directory: /home/tkloczko/rpmbuild/BUILD/okteta-0.26.10/x86_64-redhat-linux-gnu Test project /home/tkloczko/rpmbuild/BUILD/okteta-0.26.10/x86_64-redhat-linux-gnu Start 1: libkasten-core-testdocumenttest Start 2: libkasten-core-testdocumentfilesynchronizertest Start 3: libkasten-core-testdocumentfilesynchronizerfactorytest Start 4: libkasten-core-documentmanagertest Start 5: libpiecetable-piecetest Start 6: libpiecetable-piecetabletest Start 7: libpiecetable-testpiecetablechangetest Start 8: libpiecetable-testpiecetablechangeabstractpiecetablechangeiftest Start 9: libpiecetable-insertpiecetablechangeabstractpiecetablechangeiftest Start 10: libpiecetable-removepiecetablechangeabstractpiecetablechangeiftest Start 11: libpiecetable-replacepiecetablechangeabstractpiecetablechangeiftest Start 12: libpiecetable-swaprangespiecetablechangeabstractpiecetablechangeiftest Start 13: libpiecetable-grouppiecetablechangetest Start 14: libpiecetable-piecetablechangehistorytest Start 15: libpiecetable-revertablepiecetabletest Start 16: libokteta-core-arraychangemetricstest Start 17: libokteta-core-addressrangetest Start 18: libokteta-core-addressrangelisttest Start 19: libokteta-core-fixedsizebytearraymodeltest Start 20: libokteta-core-fixedsizebytearraymodelabstractbytearraymodeliftest Start 21: libokteta-core-bytearraymodeltest Start 22: libokteta-core-bytearraymodelabstractbytearraymodeliftest Start 23: libokteta-core-piecetablebytearraymodelabstractbytearraymodeliftest Start 24: libokteta-core-piecetablebytearraymodelversionableiftest Start 25: libokteta-core-valuecodectest Start 26: libokteta-core-charcodectest Start 27: libokteta-core-textcharcodectest Start 28: libokteta-core-textcharcodeccharcodeciftest Start 29: libokteta-core-ebcdic1047charcodeccharcodeciftest Start 30: libokteta-core-bookmarktest Start 31: libokteta-core-bookmarklisttest Start 32: libokteta-gui-selectiontest Start 33: libokteta-gui-coordtest Start 34: libokteta-gui-coordrangetest Start 35: libokteta-gui-coordrangelisttest Start 36: libokteta-gui-bytearraytablelayouttest Start 37: libokteta-gui-bytearraytablecursortest Start 38: oktetakasten-document-bytearraydocumenttest Start 39: oktetakasten-document-bytearraydocumentfactorytest Start 40: oktetakasten-io-bytearrayrawfilesynchronizertest Start 41: oktetakasten-io-bytearrayrawfilesynchronizerfactorytest Start 42: structures-primitivearraytest Start 43: structures-arraydatainformationtest Start 44: structures-basicdatainformationtest Start 45: structures-primitivedatainformationtest Start 46: structures-scriptclassestest Start 47: structures-uniondatainformationtest Start 48: structures-allprimitivetypestest 1/56 Test #1: libkasten-core-testdocumenttest .. Passed0.09 sec Start 49: structures-scriptvalueconvertertest 2/56 Test #2: libkasten-core-testdocumentfilesynchronizertest ..***Failed0.09 sec * Start testing of TestDocumentFileSynchronizerTest * Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 13.0.1 20230404 (Red Hat 13.0.1-0)), fedora 39 PASS : TestDocumentFileSynchronizerTest::initTestCase() PASS : TestDocumentFileSynchronizerTest::testLoadFromFile() FAIL! : TestDocumentFileSynchronizerTest::testLoadSaveFile() 'testDocument != nullptr' returned FALSE. () Loc: [/home/tkloczko/rpmbuild/BUILD/okteta-0.26.10/libs/kasten/core/tests/testdocumentfilesynchronizertest.cpp(80)] QWARN : TestDocumentFileSynchronizerTest::testLoadReloadFile() QIODevice::write (QFile, "/home/tkloczko/.kde-unit-test/testdocumentfile1synchronizertest/test1.data"): device not open FAIL! : TestDocumentFileSynchronizerTest::testLoadReloadFile() 'testDocument != nullptr' returned FALSE. () Loc: [/home/tkloczko/rpmbuild/BUILD/okteta-0.26.10/libs/kasten/core/tests/testdocumentfilesynchronizertest.cpp(164)] QWARN : TestDocumentFileSynchronizerTest::testChangeFile()
[okteta] [Bug 467541] 0.26.10: Test suite is failing
https://bugs.kde.org/show_bug.cgi?id=467541 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 467541] 0.26.10: Test suite is failing
https://bugs.kde.org/show_bug.cgi?id=467541 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 467541] 0.26.10: Test suite is failing
https://bugs.kde.org/show_bug.cgi?id=467541 --- Comment #3 from kloczek --- (In reply to Friedrich W. H. Kossebau from comment #1) [..] > In case the duplicated path separators are an issue here (bad in any case), > I pushed a commit to current 0.26 branch here: > https://invent.kde.org/utilities/okteta/-/commit/ > 67b3bb25b9fe8ce6794fa8038347a5adb4466478 > > Could you try again with that commit? Looks like that commit fixed fail of one unit + cd okteta-0.26.10 + xvfb-run -a /usr/bin/ctest --test-dir x86_64-redhat-linux-gnu --output-on-failure --force-new-ctest-process -j48 ' ' Internal ctest changing into directory: /home/tkloczko/rpmbuild/BUILD/okteta-0.26.10/x86_64-redhat-linux-gnu Test project /home/tkloczko/rpmbuild/BUILD/okteta-0.26.10/x86_64-redhat-linux-gnu Start 1: libkasten-core-testdocumenttest Start 2: libkasten-core-testdocumentfilesynchronizertest Start 3: libkasten-core-testdocumentfilesynchronizerfactorytest Start 4: libkasten-core-documentmanagertest Start 5: libpiecetable-piecetest Start 6: libpiecetable-piecetabletest Start 7: libpiecetable-testpiecetablechangetest Start 8: libpiecetable-testpiecetablechangeabstractpiecetablechangeiftest Start 9: libpiecetable-insertpiecetablechangeabstractpiecetablechangeiftest Start 10: libpiecetable-removepiecetablechangeabstractpiecetablechangeiftest Start 11: libpiecetable-replacepiecetablechangeabstractpiecetablechangeiftest Start 12: libpiecetable-swaprangespiecetablechangeabstractpiecetablechangeiftest Start 13: libpiecetable-grouppiecetablechangetest Start 14: libpiecetable-piecetablechangehistorytest Start 15: libpiecetable-revertablepiecetabletest Start 16: libokteta-core-arraychangemetricstest Start 17: libokteta-core-addressrangetest Start 18: libokteta-core-addressrangelisttest Start 19: libokteta-core-fixedsizebytearraymodeltest Start 20: libokteta-core-fixedsizebytearraymodelabstractbytearraymodeliftest Start 21: libokteta-core-bytearraymodeltest Start 22: libokteta-core-bytearraymodelabstractbytearraymodeliftest Start 23: libokteta-core-piecetablebytearraymodelabstractbytearraymodeliftest Start 24: libokteta-core-piecetablebytearraymodelversionableiftest Start 25: libokteta-core-valuecodectest Start 26: libokteta-core-charcodectest Start 27: libokteta-core-textcharcodectest Start 28: libokteta-core-textcharcodeccharcodeciftest Start 29: libokteta-core-ebcdic1047charcodeccharcodeciftest Start 30: libokteta-core-bookmarktest Start 31: libokteta-core-bookmarklisttest Start 32: libokteta-gui-selectiontest Start 33: libokteta-gui-coordtest Start 34: libokteta-gui-coordrangetest Start 35: libokteta-gui-coordrangelisttest Start 36: libokteta-gui-bytearraytablelayouttest Start 37: libokteta-gui-bytearraytablecursortest Start 38: oktetakasten-document-bytearraydocumenttest Start 39: oktetakasten-document-bytearraydocumentfactorytest Start 40: oktetakasten-io-bytearrayrawfilesynchronizertest Start 41: oktetakasten-io-bytearrayrawfilesynchronizerfactorytest Start 42: structures-primitivearraytest Start 43: structures-arraydatainformationtest Start 44: structures-basicdatainformationtest Start 45: structures-primitivedatainformationtest Start 46: structures-scriptclassestest Start 47: structures-uniondatainformationtest Start 48: structures-allprimitivetypestest 1/56 Test #1: libkasten-core-testdocumenttest .. Passed0.08 sec Start 49: structures-scriptvalueconvertertest 2/56 Test #2: libkasten-core-testdocumentfilesynchronizertest ..***Failed0.08 sec * Start testing of TestDocumentFileSynchronizerTest * Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 13.0.1 20230304 (Red Hat 13.0.1-0)), fedora 39 PASS : TestDocumentFileSynchronizerTest::initTestCase() PASS : TestDocumentFileSynchronizerTest::testLoadFromFile() FAIL! : TestDocumentFileSynchronizerTest::testLoadSaveFile() 'testDocument != nullptr' returned FALSE. () Loc: [/home/tkloczko/rpmbuild/BUILD/okteta-0.26.10/libs/kasten/core/tests/testdocumentfilesynchronizertest.cpp(80)] QWARN : TestDocumentFileSynchronizerTest::testLoadReloadFile() QIODevice::write (QFile, "/home/tkloczko/.kde-unit-test/testdocumentfile1synchronizertest/test1.data"): device not open FAIL! : TestDocumentFileSynchronizerTest::testLoadReloadFile() 'testDocument != nullptr' returned FALSE. () Loc: [/home/tkloczko/rpmbuild/BUILD/okteta-0.26.10/libs/kasten/core/tests/testdocumentfilesynchronizertest.cpp(164)] QWARN : TestDocumentFileSynchronizerTest::testChangeFile() QIODevice::write (QFile,
[okteta] [Bug 467541] 0.26.10: Test suite is failing
https://bugs.kde.org/show_bug.cgi?id=467541 --- Comment #2 from kloczek --- (In reply to Friedrich W. H. Kossebau from comment #1) [..] > What Qt version are you using? 5.15.8 > The following looks suspicious: > QWARN : TestDocumentFileSynchronizerTest::testLoadReloadFile() > QIODevice::write (QFile, > "/home/tkloczko//.kde-unit-test//testdocumentfile1synchronizertest//test1. > data"): device not open > > In case the duplicated path separators are an issue here (bad in any case), > I pushed a commit to current 0.26 branch here: > https://invent.kde.org/utilities/okteta/-/commit/ > 67b3bb25b9fe8ce6794fa8038347a5adb4466478 Will back shortly with result. > Could you try again with that commit? > > The other question would be: is home/tkloczko/.kde-unit-test/ writable > during your test runs? Yes it is writeable. -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 467541] 0.26.10: Test suite is failing
https://bugs.kde.org/show_bug.cgi?id=467541 Friedrich W. H. Kossebau changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|NEEDSINFO --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for the report. Cannot reproduce though, and has been passing for me locally (openSUSE TW) and on KDE CI all the time. See e.g. https://invent.kde.org/utilities/okteta/-/pipelines/302655/test_report for the last pipeline on the tag itself. What Qt version are you using? The following looks suspicious: QWARN : TestDocumentFileSynchronizerTest::testLoadReloadFile() QIODevice::write (QFile, "/home/tkloczko//.kde-unit-test//testdocumentfile1synchronizertest//test1.data"): device not open In case the duplicated path separators are an issue here (bad in any case), I pushed a commit to current 0.26 branch here: https://invent.kde.org/utilities/okteta/-/commit/67b3bb25b9fe8ce6794fa8038347a5adb4466478 Could you try again with that commit? The other question would be: is home/tkloczko/.kde-unit-test/ writable during your test runs? -- You are receiving this mail because: You are watching all bug changes.
