Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99162 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62709 invoked from network); 25 May 2017 00:09:24 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 May 2017 00:09:24 -0000 X-Host-Fingerprint: 2.24.106.127 unknown Received: from [2.24.106.127] ([2.24.106.127:23729] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6F/B1-10292-2B026295 for ; Wed, 24 May 2017 20:09:24 -0400 Message-ID: <6F.B1.10292.2B026295@pb1.pair.com> To: internals@lists.php.net References: <1495067758.9756.47.camel@schlueters.de> <1495103485.9756.58.camel@schlueters.de> Date: Thu, 25 May 2017 01:09:19 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 MIME-Version: 1.0 In-Reply-To: <1495103485.9756.58.camel@schlueters.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Posted-By: 2.24.106.127 Subject: Re: [PHP-DEV] Implement formal process for run-tests.php refactor From: ajf@ajf.me (Andrea Faulds) Hi all, Johannes Schlüter wrote: > phpUnit might be battle tested with parallelization, the PHP test suite > isn't. There are tons of tests using the same resource (i.e. different > mysqli and pdo_mysql tests might use the same tables some other tests > use same port for some socket stuff etc.) Would be great if we get > parallelization, though. It occurred to me a little while ago that if we ran the test suite in parallel, but only run one test from a given directory (or extension) at a time, it should probably avoid any such problems, and it would not be particularly difficult to implement. Is that worth a shot, do you think? -- Andrea Faulds https://ajf.me/