Content-Transfer-Encoding: binary X-RT-Original-Encoding: utf-8 Message-ID: X-RT-Interface: Web In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Disposition: inline MIME-Version: 1.0 References: X-Mailer: MIME-tools 5.508 (Entity 5.508) RT-Send-CC: Content-Length: 1017 On Wed Nov 15 09:24:16 2017, fdupont wrote: > On Wed Nov 15 07:18:41 2017, ondrej wrote: > > JFTR allow_query serve-stale rpzrecurse have already been modify to > > run in parallel. > > > > Note: I think the random port allocation is enough for the tests, but > > if you want to make it more robust a script that would lock, allocate, > > check the port, unlock should be made. But I strongly believe it's > > not necessary for low number of tests and 32k ports available. > > => 32k available but 1/2 collision probability after ~180 ports. We have 103 system tests now and only the most time critical are being ported. > More seriously I really prefer the "more robust" option as I > run tests on an other purpose machine. BTW a feature which > is very useful in some cases should come for free (i.e. just > check it works) with random is to be able to run simultaneously; > the same test on different builds. If you provide the script that will print the usable port number to stdout, we would integrate it.