> -----Original Message----- > From: Rasmus Lerdorf [mailto:ras...@lerdorf.com] > Sent: Thursday, May 25, 2017 3:08 PM > To: Nikita Popov <nikita....@gmail.com> > Cc: Andrea Faulds <a...@ajf.me>; PHP internals <internals@lists.php.net> > Subject: Re: [PHP-DEV] Implement formal process for run-tests.php refactor > > On Thu, May 25, 2017 at 3:52 PM, Nikita Popov <nikita....@gmail.com> wrote: > > > > > > During normal development I usually only run either Zend/ tests, or > > the tests in the extension I'm modifying (the rest is what CI is for). > > Parallelizing by directory will speed up our CI builds (which is > > important, we're often suffering from timeouts), but probably not help > > much during development. > > > > The best way to address that is probably to split some of those 1600 general > Zend/tests into sub-directories to get better concurrency when running all the > Zend tests. I think we are in for a world of hurt if we try to run adjacent > tests in > parallel. Anything that hits any sort of datastore, even if it is just the > filesystem, > will break badly. > On the other hand, there is a number of isolated tests that won't hurt parallelism. I've suggested a section like --PARALLEL-- already, but maybe it'd be also more simple to have an extra subdir in every tests dir, like Zend/tests/parallel, where only the capable tests would lay. In that case, the tests itself wouldn't have be touched, just verified and moved into parallel subdir if suitable. An approach with the section would require to edit the test file, but the advantage would be that the file doesn't have to be moved. Either way, there's a work to verify and adapt tests to the choosen approach.
Regards Anatol
