Message261095
Alex - The usual cause for that problem isn't regrtest (at least, not directly). The cause is one of the tests in the suite spawning a subprocess. Due to the way the test harness works, when the test suite forks/spawns a subprocess (e.g., to run a network server or a multiprocess worker), the fork causes the a second version of the test suite to start, rather than starting the server subprocess.
I've attached a patch for 3.5.1. This includes a patch to work around Issue22625; the patch is definitely suboptimal, but it lets a build come to completion. What is really needed (as requested on python-dev) is some help working out how to fix Issue22625 properly. |
|
Date |
User |
Action |
Args |
2016-03-02 01:36:59 | freakboy3742 | set | recipients:
+ freakboy3742, doko, ronaldoussoren, ncoghlan, ned.deily, r.david.murray, bkabrda, Lukasa, rkuska, mpaolini, Alex.Willmer |
2016-03-02 01:36:55 | freakboy3742 | set | messageid: <1456882615.71.0.567009958144.issue23670@psf.upfronthosting.co.za> |
2016-03-02 01:36:54 | freakboy3742 | link | issue23670 messages |
2016-03-02 01:36:54 | freakboy3742 | create | |
|