Closed maxs-rose closed 1 year ago
I have found our issue. Turns out some of our tests were opening new tabs and as a result firefox was very aggressively throttling karma.
Fixing these tests to not actually open a new browser tab means the firefox texts are now more inline with chrome in terms to speed with firefox now only being about 40s behind chrome.
That's great news. Thank you for following up on this.
Our Angular unit tests are being run on both Firefox and Chrome but Firefox is much slower than Chrome.
When running locally with
ng test
:Locally Firefox is installed inside WSL whilst Chrome is using the version installed in windows.
During our CI pipelines Firefox and Chrome are run separately and we are getting execution times of: Firefox:
Finished in 7 mins 52.707 secs / 6 mins 29.502 secs
Chrome:Finished in 3 mins 5.856 secs / 2 mins 38.854 secs
Firefox and Chrome are both running separately in Docker container for CI with a test concurrency of 1.
More recently Firefox is just disconnecting part way through the CI run causing the pipeline to fail:
Is there any advice to attempt to resolve this issue?