-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libregrtest: mark a test as failed if a thread logs an unexpected exception #88009
Comments
The Python test runner (libregrtest) should mark a test as failed if a thread logs an unexpected exception, as already done with unraisable exception. See for example bpo-43842 where test_logging logs the following exception, but the tes is marked as passed: Exception in thread Thread-25 (serve_forever):
Traceback (most recent call last):
File "/usr/home/vstinner/python/master/Lib/threading.py", line 990, in _bootstrap_inner
self.run()
File "/usr/home/vstinner/python/master/Lib/threading.py", line 928, in run
self._target(*self._args, **self._kwargs)
File "/usr/home/vstinner/python/master/Lib/test/test_logging.py", line 863, in serve_forever
asyncore.loop(poll_interval, map=self._map)
File "/usr/home/vstinner/python/master/Lib/asyncore.py", line 203, in loop
poll_fun(timeout, map)
File "/usr/home/vstinner/python/master/Lib/asyncore.py", line 144, in poll
r, w, e = select.select(r, w, e, timeout)
OSError: [Errno 9] Bad file descriptor Attached PR implements this change. |
test_concurrent_futures logs two warnings. s390x Debian 3.x: AMD64 RHEL7 3.x: 0:03:18 load avg: 4.78 [302/427] test_concurrent_futures passed (2 min 46 sec) -- running: test_tokenize (37.8 sec), test_peg_generator (59.2 sec) |
test_concurrent_futures logs two warnings: I created bpo-43867 for this one. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: