Running concurrency

[djones8520]

Does the order of arguments matter? I've tried a few different combos, but a couple are:

vendor/bin/peridot -c tests/unit/peridot.php tests/unit --concurrent
vendor/bin/peridot -c tests/unit/peridot.php tests/unit --concurrent -p2

I get the message: Starting workers on 2/5 processes

But after that, nothing happens.

Thanks for any suggestions.

Edit: I just noticed the Usage that says the files should be after the options. I also tried the options first:
vendor/bin/peridot -c tests/unit/peridot.php --concurrent -p2 tests/unit

[brianium]

@djones8520 I think there is an open issue with regards to the config file switch, I wonder if it is reading your config file. Any way you can hoist your config up to the current directory you are running the tests from just to see if it changes anything?

[djones8520]

Same issue. I'm not sure if I'm misunderstanding what you mean about not being able to read the config file or not, but I think it is reading the file, because I do not see the concurrency options unless I put the new ConCurrencyPlugin line in the config file.

[brianium]

I was thinking more the workers were unable to locate the config file. Not entirely sure what's going on. I will try testing against the latest version of peridot to see if anything has changed

[djones8520]

Just an fyi, we have peridot ~1.0 in composer, so we are not running the latest version. It's something I'm looking to update soon, so perhaps that would help.

[brianium]

That should cover the latest I would think. ~ is next significant release i believe. What version do you get when you do peridot -V?

[djones8520]

1.17. I guess that is the latest version. In looking into our scope issue, I saw a issue/comment about 2.0, so I assumed 2.something was the latest version.