Hello Dan, or anyone else affected, Accepted umockdev into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/umockdev/0.11.1-1ubuntu0.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to umockdev in Ubuntu. https://bugs.launchpad.net/bugs/1831467 Title: test-umockdev tests flaky on armhf (and sometimes other archs) Status in umockdev package in Ubuntu: Fix Released Status in umockdev source package in Xenial: In Progress Status in umockdev source package in Bionic: Fix Committed Status in umockdev source package in Focal: Fix Committed Status in umockdev source package in Groovy: Fix Released Bug description: [impact] these tests fail intermittently, due to various timing issues, as well as an actual code bug in how data fuzz is calculated. it looks like the failures are mostly on armhf, but do happen less often on other archs. [test case] check the previous autopkgtest logs, e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/armhf/u/umockdev/20190601_015323_8f795@/log.gz [regression potential] any regression would likely result in incorrectly failing/passing autopkgtests, or in a incorrect pass or incorrect fail of the ScriptRunner to verify the data's level of fuzz. [scope] as the tests are flaky on armhf all the way back to trusty, this is needed for all releases. [other info] Fixed upstream in PR https://github.com/martinpitt/umockdev/pull/103 Most of the changes are test case fixes, but there is one fix to source code to fix the ScriptRunning function that validates the level of fuzz in data, so this is not *only* a testcase fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1831467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
