Your message dated Mon, 3 Dec 2018 11:24:15 -0300 with message-id <20181203142414.znbh5sil2p4sxrmt@neoptolemo.gnuservers.com.ar> and subject line Re: Bug#906694: purpose: autopkgtest regression has caused the Debian Bug report #906694, regarding purpose: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 906694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906694 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: purpose: autopkgtest regression
- From: Paul Gevers <elbrus@debian.org>
- Date: Sun, 19 Aug 2018 21:27:02 +0200
- Message-id: <1be32a76-e829-c7c6-9b72-5804c357e79d@debian.org>
Source: purpose Version: 5.49.0-1 X-Debbugs-CC: debian-ci@lists.debian.org User: debian-ci@lists.debian.org Usertags: regression Dear maintainers, With the upload of 5.49.0-1 the autpkgtest of your package started to fail in unstable and testing. I copied the output below. Currently this regression is contributing to the delay of the migration to testing [1]. Could you please investigate the situation and fix it? If needed, please change the bug's severity as appropriate. Two days ago there has been quite some uploads in the KDE stack which triggered a lot of regressions, which seem to be resolved once all packages were build. This regression however seems to remain, I am totally sure if it is not merely waiting for some other package, but I don't think so. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=purpose https://ci.debian.net/data/autopkgtest/testing/amd64/p/purpose/845553/log.gz autopkgtest [06:34:59]: test testsuite: [----------------------- Openbox-Message: Unable to find a valid menu file "/var/lib/openbox/debian-menu.xml" libKF5Parts.so.5 was not found. libKF5Plasma.so.5 was not found. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher' kdeinit5: Launched KLauncher, pid = 20492, result = 0 Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kdeinit5: opened connection to :99 cd obj-x86_64-linux-gnu && make -j2 test ARGS\+=-j2 Running tests... /usr/bin/ctest --force-new-ctest-process -j2 Test project /tmp/autopkgtest-lxc.ob13vu9y/downtmp/build.g9E/src/obj-x86_64-linux-gnu Start 1: alternativesmodeltest Start 2: menutest kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' kf5.kio.kio_http: Can't communicate with kded_kcookiejar! kf5.kio.kio_http: Can't communicate with kded_kcookiejar! kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' kf5.kio.kio_http: Can't communicate with kded_kcookiejar! kf5.kio.kio_http: Can't communicate with kded_kcookiejar! kf5.kio.kio_file: Couldn't rename "/tmp/purposetest.part" to "/tmp/purposetest" kdeinit5: PID 20520 terminated. kdeinit5: PID 20531 terminated. kdeinit5: PID 20521 terminated. 1/2 Test #2: menutest .........................***Failed 2.50 sec ********* Start testing of MenuTest ********* Config: Using QtTest library 5.11.1, Qt 5.11.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 8.1.0) PASS : MenuTest::initTestCase() QWARN : MenuTest::runJobTest() qrc:/org/kde/purpose/RunningJob.qml:46:16: Unable to assign ulong to double QWARN : MenuTest::runJobTest() kf5.kservice.services: KMimeTypeTrader: couldn't find service type "KParts/ReadOnlyPart" Please ensure that the .desktop file for it is installed; then run kbuildsycoca5. QDEBUG : MenuTest::runJobTest() job failed with error " /tmp/purposetest" FAIL! : MenuTest::runJobTest() Compared values are not the same Actual (error): 157 Expected (0) : 0 Loc: [/tmp/autopkgtest-lxc.ob13vu9y/downtmp/build.g9E/src/autotests/menutest.cpp(74)] PASS : MenuTest::cleanupTestCase() Totals: 2 passed, 1 failed, 0 skipped, 0 blacklisted, 2414ms ********* Finished testing of MenuTest ********* kdeinit5: PID 20515 terminated. kdeinit5: PID 20513 terminated. 2/2 Test #1: alternativesmodeltest ............ Passed 3.07 sec 50% tests passed, 1 tests failed out of 2 Total Test time (real) = 3.08 sec The following tests FAILED: 2 - menutest (Failed) Errors while running CTest make: *** [Makefile:133: test] Error 8 dh_auto_test: cd obj-x86_64-linux-gnu && make -j2 test ARGS\+=-j2 returned exit code 2 kdeinit5: PID 20530 terminated. kdeinit5: terminate KDE. klauncher: Exiting on signal 1 autopkgtest [06:35:04]: test testsuite: -----------------------]Attachment: signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
- To: Paul Gevers <elbrus@debian.org>, 906694-done@bugs.debian.org
- Subject: Re: Bug#906694: purpose: autopkgtest regression
- From: Maximiliano Curia <maxy@gnuservers.com.ar>
- Date: Mon, 3 Dec 2018 11:24:15 -0300
- Message-id: <20181203142414.znbh5sil2p4sxrmt@neoptolemo.gnuservers.com.ar>
- In-reply-to: <1be32a76-e829-c7c6-9b72-5804c357e79d@debian.org>
- References: <1be32a76-e829-c7c6-9b72-5804c357e79d@debian.org>
Version: 5.51.0-1 ¡Hola Paul! El 2018-08-19 a las 21:27 +0200, Paul Gevers escribió:With the upload of 5.49.0-1 the autpkgtest of your package started to fail in unstable and testing. I copied the output below.Currently this regression is contributing to the delay of the migration to testing [1]. Could you please investigate the situation and fix it? If needed, please change the bug's severity as appropriate.Two days ago there has been quite some uploads in the KDE stack which triggered a lot of regressions, which seem to be resolved once all packages were build. This regression however seems to remain, I am totally sure if it is not merely waiting for some other package, but I don't think so.More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformationThe regression seems to be reverted in 5.51, thus closing the issue.About the kde frameworks uploads, they are handled in a bundle, and breaks and dependencies are added so they migrate to testing as needed, the same breaks and dependencies can cause temporary uninstallability in unstable, thus, having a lot of temporary regressions, in order to have a "smoother" testing.At the same time, the autopkgtest run (mostly) upstream's unittests (mostly the ones that can't be run as part of the build). But, sadly, upstream doesn't enforce running their unittests as part of their development nor release process, so, some regressions in part of their unittests is "normal". This fits "nicely" with the current way Debian delays the transitions to testing, which gives enough time to unstable users to report real regressions in behaviour.All of this is to explain that, currently, a report about autopkgtest issues is not really useful to us, and would be time better spent reporting them directly upstream (if it applies). Furthermore, once the autopkgtest are used to block the migration to testing completely, we would be forced to to simply drop most of the tests (as long as upstream doesn't change their policy regarding unittest).This can be considered as a documentation of the current state of affairs regarding kde frameworks and kde plasma. No response needed.Happy hacking, -- "Anytime you have a fifty-fifty chance of getting something right, there's a 90 percent probability you'll get it wrong." -- The 50-50-90 rule Saludos /\/\ /\ >< `/Attachment: signature.asc
Description: PGP signature
--- End Message ---