Message297464
| Author |
martin.panter |
| Recipients |
martin.panter, vstinner |
| Date |
2017年07月01日.01:26:21 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1498872382.31.0.0778620280192.issue30391@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
These tests are supposed to:
1. Create a TCP server
2. Open a TCP connection
3. Run a custom connection handler (depending on the particular test) in a new thread
4. When the handler returns, the new thread should call "shutdown_request"
5. Shutdown_request closes the server’s connection socket
6. Shutdown_request sets an event for the main thread
7. Main thread waits for the above event
The stack trace indicates a thread is stuck at step 7. My guess is that step 5 has raised an exception, killing the thread rather than continuing to step 6. I suspect it is a "socket.close" call raising an asynchronous error such as ECONNRESET; see Issue 30319. A general fix for that problem might fix these test_socketserver hangs. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2017年07月01日 01:26:22 | martin.panter | set | recipients:
+ martin.panter, vstinner |
| 2017年07月01日 01:26:22 | martin.panter | set | messageid: <1498872382.31.0.0778620280192.issue30391@psf.upfronthosting.co.za> |
| 2017年07月01日 01:26:22 | martin.panter | link | issue30391 messages |
| 2017年07月01日 01:26:21 | martin.panter | create |
|