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 | mark.dickinson |
|---|---|
| Recipients | mark.dickinson, neologix, nnorwitz, pitrou, r.david.murray, skrah, srid, vstinner |
| Date | 2010年04月13日.13:20:33 |
| SpamBayes Score | 0.00038074492 |
| Marked as misclassified | No |
| Message-id | <1271164835.5.0.175250282501.issue4970@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Results of my simple-minded strategy (see r80033-4, r80037, r80042, r80045, r80047-51): test_execvpe_with_bad_program in ExecTests by itself is enough to trigger the signal 32 error (in combination with test_wait3). See: http://www.python.org/dev/buildbot/builders/x86%20gentoo%203.x/builds/2174 If just this single test is disabled and all other tests in test_os are allowed to run, there's no problem (at least with test_wait3; (I haven't tried re-enabling *all* other tests in the test suite yet). See: http://www.python.org/dev/buildbot/builders/x86%20gentoo%203.x/builds/2176 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010年04月13日 13:20:35 | mark.dickinson | set | recipients: + mark.dickinson, nnorwitz, pitrou, vstinner, r.david.murray, srid, skrah, neologix |
| 2010年04月13日 13:20:35 | mark.dickinson | set | messageid: <1271164835.5.0.175250282501.issue4970@psf.upfronthosting.co.za> |
| 2010年04月13日 13:20:33 | mark.dickinson | link | issue4970 messages |
| 2010年04月13日 13:20:33 | mark.dickinson | create | |