Message321783
Huh, that's weird. My first thought was some kind of race condition, but... raise_signal uses raise(), which on Windows should be invoking the signal handler synchronously, so the warning should definitely be printed before raise_signal() returns.
Could the warning be trapped in some buffer? That would be weird too, usually stderr and warnings should not be buffered.
Of course putting a retry loop around the test is an option if we can't figure out how to fix it properly. |
|
Date |
User |
Action |
Args |
2018-07-17 00:43:00 | njs | set | recipients:
+ njs, pitrou, vstinner |
2018-07-17 00:43:00 | njs | set | messageid: <1531788180.59.0.56676864532.issue34130@psf.upfronthosting.co.za> |
2018-07-17 00:43:00 | njs | link | issue34130 messages |
2018-07-17 00:42:59 | njs | create | |
|