Package: python-oslo.concurrency / 7.2.0-4
Metadata
| Package | Version | Patches format |
|---|---|---|
| python-oslo.concurrency | 7.2.0-4 | 3.0 (quilt) |
Patch series
view the series file| Patch | File delta | Description |
|---|---|---|
| fix tests i386.patch | (download) |
oslo_concurrency/tests/unit/test_processutils.py |
3 2 + 1 - 0 ! |
strip long integer suffix from strings. a proper fix would be
more involved so I've opened a bug upstream.
Bug-Ubuntu: https://bugs.launchpad.net/bugs/1552690
Bug-Debian: https://bugs.debian.org/880227
|
| py3.14_fix_multiprocessing_spawn_failure_in_FileBasedLockingTestCase.patch | (download) |
oslo_concurrency/tests/unit/test_lockutils.py |
32 20 + 12 - 0 ! |
fix multiprocessing spawn failure in filebasedlockingtestcase In Python 3.8+ (and now default in Debian/Python 3.14), multiprocessing uses the 'spawn' or 'forkserver' start methods. With these methods, all arguments to Process, including the target function, must be picklable. . The test FileBasedLockingTestCase.test_interprocess_nonblocking_external_lock was previously defining both the target function `other` and the locked function `foo` as **local functions** inside the test method. Under spawn/forkserver, local functions cannot be pickled, which caused PicklingError when starting the subprocess. . This patch moves the process target to a module-level helper function and defines the called function `foo` inside that helper. The helper takes the shared multiprocessing.Value and the lock directory as arguments, allowing the subprocess to run the same locking logic safely. . No behavioral change in the test, only fixes Python 3.14 spawn compatibility. Signed-off-by: Thomas Goirand <zigo@debian.org> |
1
