Message321785
| Author | nascheme |
|---|---|
| Recipients | nascheme, vstinner |
| Date | 2018-07-17.01:50:02 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1531792203.21.0.56676864532.issue31342@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Yes, it looks like the same issue as bpo-29512. Renaming test.bisect is the simplest solution. I have trained myself to run "python -m test.regrtest <test name>" so this issue doesn't affect me any more. However, I think it was a trap that will catch some people. So, thanks for fixing. I considered adding a 'bisect' command to the test/__main__, e.g. you could run 'python -m test --bisect ..'. That looks not entirely simple to implement though. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-07-17 01:50:03 | nascheme | set | recipients: + nascheme, vstinner |
| 2018-07-17 01:50:03 | nascheme | set | messageid: <1531792203.21.0.56676864532.issue31342@psf.upfronthosting.co.za> |
| 2018-07-17 01:50:03 | nascheme | link | issue31342 messages |
| 2018-07-17 01:50:02 | nascheme | create | |