This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | vstinner |
|---|---|
| Recipients | davin, paul.moore, steve.dower, tim.golden, vstinner, zach.ware |
| Date | 2017年04月26日.13:23:34 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1493213014.57.0.778185654451.issue30169@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I also checked the last 250 builds of AMD64 Windows8 3.x: test_multiprocessing_spawn never crashed. http://buildbot.python.org/all/builders/AMD64%20Windows8%203.x We got 8 crashed on "AMD64 Windows8.1 Non-Debug 3.x", but 0 crash on "AMD64 Windows8 3.x" (similar Windows version, but it's a different buildbot slave, so different hardware, version, etc.)... So *maybe* it's related to the commit a00c3fd12d421e41b769debd7df717d17b0deed5 and the issue #29941 since this patch changed the behaviour of Python compiled in release mode. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017年04月26日 13:23:34 | vstinner | set | recipients: + vstinner, paul.moore, tim.golden, zach.ware, steve.dower, davin |
| 2017年04月26日 13:23:34 | vstinner | set | messageid: <1493213014.57.0.778185654451.issue30169@psf.upfronthosting.co.za> |
| 2017年04月26日 13:23:34 | vstinner | link | issue30169 messages |
| 2017年04月26日 13:23:34 | vstinner | create | |