Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:100849 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 13338 invoked from network); 10 Oct 2017 12:09:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Oct 2017 12:09:18 -0000 Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 84.19.169.162 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 84.19.169.162 mail.experimentalworks.net Received: from [84.19.169.162] ([84.19.169.162:38356] helo=mail.experimentalworks.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CD/96-49033-C68BCD95 for ; Tue, 10 Oct 2017 08:09:17 -0400 Received: from kuechenschabe.fritz.box (ppp-46-244-176-141.dynamic.mnet-online.de [46.244.176.141]) by mail.experimentalworks.net (Postfix) with ESMTPSA id 67A5F6695B; Tue, 10 Oct 2017 14:09:13 +0200 (CEST) Message-ID: <1507637348.2615.4.camel@schlueters.de> To: Andrea Faulds , internals@lists.php.net Date: Tue, 10 Oct 2017 14:09:08 +0200 In-Reply-To: <1B.6B.16800.8BF99D95@pb1.pair.com> References: <1B.6B.16800.8BF99D95@pb1.pair.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.2-0ubuntu3.2 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] Parallelised run-tests.php (patch) From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On So, 2017-10-08 at 04:47 +0100, Andrea Faulds wrote: > Have you long since ABANDONED every test directory besides > Zend/tests? ... or ran only eext/foo/tests ;) > …*ahem*. Okay, enough terrible salesmanship. I felt like > parallelising  > run-tests.php, so I did it. If you give it the flag -jX, it'll spawn > X  > worker processes and throw batches at tests at them, and those > worker  This is cool! I also see (from very very very) short look on the github diff that you have a parallelization protection for some tests, which might share resources. Very good! Kind of unrelated: Somewhere on my 10+ years old todo list I also have the item of using FastCGI or similar for running tests to avoid running tthrough MINIT/MSHUTDOWN for each and every test (for some we can'T avoid due to ini requirements, but well) maybe a less hackish way for parallelizing might be using fpm workers and async io (just to spin the idea, maybe somebody takes it up ...) johannes