I'm experiencing the same error - when the fault is introduced it seems like the tests are just skipped.

This is the output for the suite before introducing the error.

Tests:    1190 passed (5990 assertions)
Duration: 3.83s
Parallel: 11 processes

This is the output for the suite after introducing the error.

Tests:    1062 passed (5862 assertions)
Duration: 3.88s
Parallel: 11 processes

It looks like 128 tests have disappeared, but no failures at all.
Running the tests without --parallel will instantly crash with the error being outputted.

Edit: I'm using Pest 3.2

I'm experiencing the same error - when the fault is introduced it seems like the tests are just skipped.

This is the output for the suite before introducing the error.

Tests:    1190 passed (5990 assertions)
Duration: 3.83s
Parallel: 11 processes

This is the output for the suite after introducing the error.

Tests:    1062 passed (5862 assertions)
Duration: 3.88s
Parallel: 11 processes

It looks like 128 tests have disappeared, but no failures at all. Running the tests without --parallel will instantly crash with the error being outputted.

Edit: I'm using Pest 3.2

Yes. I used an inexistent dataset in the example, but it also happens if the test fails. This is pretty huge, actually. We need to choose between running with --parallel, but being aware that we won't know if dataset tests have failed. Or run it without --parallel flag, which makes testing very slow.