| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
macOS job failed with: 0:05:19 load avg: 9.67 [ 99/436/1] test_concurrent_futures failed (env changed) (3 min 15 sec) (...) Warning -- sys.stderr was modified by test_concurrent_futures Warning -- Before: <_io.StringIO object at 0x10d1a5590> Warning -- After: <_io.StringIO object at 0x10d822cb0> I don't know if it's related to the PR. |
Sorry, something went wrong.
|
PR rebased on main to get fixes for unrelated compiler warnings. |
Sorry, something went wrong.
The mutex with conditional variable implementation of lock now recomputes the timeout if acquire(timeout=timeout) is interrupted by a signal.
|
I'm no longer convinced that this change is needed:
Locks used in Python call PyThread_acquire_lock_timed() with intr_flag=1: if a function returns EINTR, it returns immediately, the caller checks for signals, and then calls again the function to try again to acquire to lock with a re-computed timeout. I close my PR. But I wrote PR #94056 to clean-up the code. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
The mutex with conditional variable implementation of lock now
recomputes the timeout if acquire(timeout=timeout) is interrupted by
a signal.