When browser disconnects, remaining tests are skipped about karma-parallel

[paulcmason]

Hi - I have setup karma-parallel on our test suite as well. Approx 2700 tests. On the first run the sharding is working great and it has massively decreased our suite run times. However as above we are getting false positives when the runner disconnects from chrome. It will run again but not run the tests in the shard that disconnected. Unfortunately this means we can't use this day to day at the moment.

[lucasklaassen]

We are running 500 tests and it has reduced our time as well but the browser disconnect issue is preventing us from running this within our CI/CD Pipeline. :(

[nickbullock]

We are running 16k tests and got the same problem as well (concurrency 2-3, chunks 200-500).
Some thoughts: we used karma-parallel for last two years in ci pipeline with our own custom webpack config for huge hybrid angular application. Now we moved to ng-cli build configuration and faced this issue. Maybe ng-cli is the root of evil.
UPD: forget it. The problem was in our docker container. Now everything works as expected.

[juanmendes]

There's a PR for this problem for this at #54

[rohitkandhal]

Is it abandoned?