On 15 Sep 2014 05:59, "Matt Ficken" wrote:
>
> In making/merging major changes (like concurrency) the most important
thing is to not break that compatibility and dependability:
>
> Your patch will fail without the /proc filesystem(mac osx?). On Windows,
you can check the %NUMBER_OF_PROCESSORS% en
When building PFTT, the PHP Full Test Tool, one goal was maximizing speed
so that we would be more likely to frequently Fully test PHP (Full-coverage
of many scenarios), and to do that I built it to run tests concurrently...
Concurrent/parallel execution can cause breaks that otherwise work with
n
On 09/07/14 22:00, Stas Malyshev wrote:
> Hi!
>
>> Having thought a bit about the subject, the heuristic I came up with was to
>> 1) do not run tests from the same extension in parallel, and 2) do not run
>> tests from certain extensions in parallel (e.g., mysql and pdo_mysql).
>
> How about ma
Hi!
> I added a CONCURRENCY_GROUP section, see
> https://github.com/m6w6/php-src/compare/parallel-run-tests?expand=1
>
> If the next test to execute is in the same CONCURRENCY_GROUP as one
> which is already/still running, it will be pushed back.
>
> So tests with f.e. listening servers could u
On Wed 09 Jul 2014 22:00:49 CEST, Stas Malyshev wrote:
> Hi!
>
>> Having thought a bit about the subject, the heuristic I came up with was to
>> 1) do not run tests from the same extension in parallel, and 2) do not run
>> tests from certain extensions in parallel (e.g., mysql and pdo_mysql).
Heur
Hi!
> Having thought a bit about the subject, the heuristic I came up with was to
> 1) do not run tests from the same extension in parallel, and 2) do not run
> tests from certain extensions in parallel (e.g., mysql and pdo_mysql).
How about making it a whitelist? For tests/extensions we know i
On Mon, Jul 7, 2014 at 6:53 AM, Michael Wallner wrote:
I also have a patch for run-tests sitting around for quite some time,
which
adds concurrent test execution support. I already fixed a lot of non
re-entrant tests in the past, but there might still be quite some of
them.
HHVM uses PHP's
On Tue, Jul 8, 2014 at 8:02 AM, Michael Wallner wrote:
>> About the need of a flag for the tests, it would be useful as well.
>> Many tests can't be in run in parallel, like many mysql tests (or
>> other databases f.e.).
>
>
> Why can't those tests use unique (to them) names?
mysql f.e. initiali
On 7 July 2014 19:13, Pierre Joye wrote:
> On Mon, Jul 7, 2014 at 5:07 PM, Laruence wrote:
> > Hey:
> >
> > On Mon, Jul 7, 2014 at 9:53 PM, Michael Wallner wrote:
> >> Hi!
> >>
> >> I also have a patch for run-tests sitting around for quite some time,
> which
> >> adds concurrent test execution
On 7 July 2014 17:17, Ferenc Kovacs wrote:
>
>
>
> On Mon, Jul 7, 2014 at 3:53 PM, Michael Wallner wrote:
>
>> Hi!
>>
>> I also have a patch for run-tests sitting around for quite some time,
>> which adds concurrent test execution support. I already fixed a lot of non
>> re-entrant tests in the
On 7 July 2014 17:07, Laruence wrote:
> Hey:
>
> On Mon, Jul 7, 2014 at 9:53 PM, Michael Wallner wrote:
> > Hi!
> >
> > I also have a patch for run-tests sitting around for quite some time,
> which
> > adds concurrent test execution support. I already fixed a lot of non
> > re-entrant tests in t
On Mon, Jul 7, 2014 at 5:07 PM, Laruence wrote:
> Hey:
>
> On Mon, Jul 7, 2014 at 9:53 PM, Michael Wallner wrote:
>> Hi!
>>
>> I also have a patch for run-tests sitting around for quite some time, which
>> adds concurrent test execution support. I already fixed a lot of non
>> re-entrant tests in
On Mon, Jul 7, 2014 at 6:53 AM, Michael Wallner wrote:
> I also have a patch for run-tests sitting around for quite some time, which
> adds concurrent test execution support. I already fixed a lot of non
> re-entrant tests in the past, but there might still be quite some of them.
>
HHVM uses PHP's
On Mon, Jul 7, 2014 at 3:53 PM, Michael Wallner wrote:
> Hi!
>
> I also have a patch for run-tests sitting around for quite some time,
> which adds concurrent test execution support. I already fixed a lot of non
> re-entrant tests in the past, but there might still be quite some of them.
>
> Test
Hey:
On Mon, Jul 7, 2014 at 9:53 PM, Michael Wallner wrote:
> Hi!
>
> I also have a patch for run-tests sitting around for quite some time, which
> adds concurrent test execution support. I already fixed a lot of non
> re-entrant tests in the past, but there might still be quite some of them.
>
>
On 7 Jul 2014, at 15:36, Michael Wallner wrote:
> Hm... didn't think of that, seems overly complex. What would actually need
> the singularity of the universe? :)
I don’t think it’d be difficult. It wouldn’t mean you can’t run tests alongside
it, just that you can’t run it concurrently with a
On Mon, Jul 7, 2014 at 9:53 PM, Michael Wallner wrote:
> Hi!
>
> I also have a patch for run-tests sitting around for quite some time, which
> adds concurrent test execution support. I already fixed a lot of non
> re-entrant tests in the past, but there might still be quite some of them.
>
> Tests
Hi Andrea!
On 7 July 2014 15:56, Andrea Faulds wrote:
>
> On 7 Jul 2014, at 14:53, Michael Wallner wrote:
> > I also have a patch for run-tests sitting around for quite some time,
> which adds concurrent test execution support. I already fixed a lot of non
> re-entrant tests in the past, but t
On 7 Jul 2014, at 14:53, Michael Wallner wrote:
> I also have a patch for run-tests sitting around for quite some time, which
> adds concurrent test execution support. I already fixed a lot of non
> re-entrant tests in the past, but there might still be quite some of them.
Did you, or will you
Hi!
I also have a patch for run-tests sitting around for quite some time, which
adds concurrent test execution support. I already fixed a lot of non
re-entrant tests in the past, but there might still be quite some of them.
Tests in ./Zend take 8 seconds instead of 30 on my box.
Please find the
20 matches
Mail list logo
