Change default console argument to auto

[andrerom]

I forgot this part in prior pull request, so doc and command is not aligned now in 2.1.

[andreasschroth]

Oops! Thank you. But could you please fix the failing tests again? TravisCI is failing...

[andreasschroth]

@andrerom Would be awesome, if you could update the failing tests. Otherwise I'll do that.

[andrerom]

I won't be able to anytime soon.

[andrerom]

@andreasschroth Fixed tests

EDIT: Failure on dev stability seems unrelated ❓

But I have no idea why the tests on travis gave following output before this fix Running phpunit in 32 processes with /home/travis/build/paratestphp/paratest/vendor/phpunit/phpunit/phpunit. Functional mode is ON.\n

As in it beats me why 32 processes where picked by auto code on Travis, I would expect far less as it's 1 or 2 cores there afaik.

So maybe we should check why this is the cases, as it seems what we read from /proc/cpuinfo reads info from host and not what we probably care for here, the guest.

[andreasschroth]

@andrerom Thanks. Regarding failing test on PHP 7.2 dev: Well I guess phpunit changed something in their method signature, is definitely unrelated to this PR.

Regarding the 32 cores I was also a bit surprised at first - and thought they might be extremely generous. But yes, I looked it up under https://docs.travis-ci.com/user/reference/overview/ and it seems that Travis VMs run on 2 cores. I find it a bit weird though that /proc/cpuinfo inside the VM contains the information about the host, how exactly can that be?

[andrerom]

how exactly can that be?

🤷‍♂️

Can't remember seeing this when testing on a ubuntu docker container locally long time ago, but as this is completely different hypervisor I'm unsure if it matters or not.

[matthewnessworthy]

The unrelated failure relates to this commit ( sebastianbergmann/phpunit@f5e5add#diff-511c90242d5589e941582006e0485184R407 ) from 3 days ago

[andreasschroth]

Sorry for late merge, changes look good and failing CI is unrelated to this PR.