Hello Kuba, or anyone else affected, Accepted ubuntu-drivers-common into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers- common/1:0.9.6.2~0.22.04.7 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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. ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2077646 Title: revert RLIMIT_NOFILE set and test Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Noble: Fix Committed Status in ubuntu-drivers-common source package in Oracular: Fix Released Bug description: change to builder config in RLIMIT_NOFILE resulted in one of the tests to fail. The original value of 1024 is now changed to 65535. ADT test framework in u-d-c is intended to rise this value to 8180, but only if it was lower than that. Then it checks that the limit is set to 8180. After the change to the builder config, the tests fail because the value is higher than 8180, but the subsequent test is still performed. Testing framework became too dependent on builder's internal config. [ Impact ] ADT testing fails, resulting in package build failures in PPA [ Test Plan ] Run ADT tests at package build time, or locally with: PYTHONPATH=. python3 tests/run test_ubuntu_drivers The message that we are looking for is: ====================================================================== FAIL: test_max_open_file_descriptors (test_ubuntu_drivers.DetectTest) max_open_file_descriptors ---------------------------------------------------------------------- Traceback (most recent call last): File "/<<PKGBUILDDIR>>/tests/test_ubuntu_drivers.py", line 209, in test_max_open_file_descriptors self.assertEqual(soft, 8180) AssertionError: 65536 != 8180 [ Where problems could occur ] during ADT testing [ Other Info ] Caused by commit: commit 95ab52ae6a00f1cd75bd842486849c0bdb74c71c Author: Alberto Milone <alberto.mil...@canonical.com> Date: Mon Mar 7 13:38:19 2022 +0100 Change maximum open files limit for the shell This patch is no longer needed and can be reverted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2077646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
