chore: throw more threads at dart test

[td-famedly]

note: this probably does not help us a lot atm given that the base github runner is a 2 core vm

[krille-chan]

So if getconf _NPROCESSORS_ONLN returns 2 in the github runner, but the default value of --concurrency=<threads> is 4, this will mean that we reduce the amount of threads instead of throwing more threads at dart test. I don't think that this will help much :-/

[td-famedly]

So if getconf _NPROCESSORS_ONLN returns 2 in the github runner, but the default value of --concurrency=<threads> is 4, this will mean that we reduce the amount of threads instead of throwing more threads at dart test. I don't think that this will help much :-/

Incorrect, the docs say. so right now it probably runs using 1 core? https://pub.dev/packages/test#test-concurrency

Test suites run concurrently by default, using half of the host's CPU cores.

[nico-famedly]

With this change:

Without:

So I would say it made it faster?

[krille-chan]

Incorrect, the docs say. so right now it probably runs using 1 core? https://pub.dev/packages/test#test-concurrency

This is the output of dart test --help:

-j, --concurrency=<threads>           The number of concurrent test suites run.
                                      (defaults to "4")

But it makes sense. Because I have 8 cores, the default is only for my machine. Sorry, I thought this "default" was meant globally :D