You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ci: fix saucelabs browser crashing due to idle timeout
In the past when the Angular Team reworked the Saucelabs
Karma launcher the Saucelabs Selenium heartbeat has been
removed in favor of people just increasing the Saucelabs
`idleTimeout` to the max minutes their test will run.
The `idleTimeout` is limited to a 16min right now, so we
need to get back to the approach relying on a Selenium heartbeat.
For reference: The heartbeat refers to the Karma launcher
performing an arbitrary Selenium command every X seconds. This
helps with keeping the Saucelabs browser alive.
Currently we exceed the `idleTimeout` of 16min and the browsers
start to crash. Karma re-starts the browser. This results in
increased time for the Saucelabs test to ~30min from ~15min. We
fix this by upating the Karma Saucelabs launcher to a version
that has been improved by the Saucelabs team. We were always
hestitant to updating because it took a lot effort to get the
Saucelabs karma launcher stable (in the past it was _super_ flaky
with the heartbeat and implementation), but it's worth another try
given we now exceed the ~16min due to more tests being added.
Long-term we want to switch the Saucelabs/Browserstack tests to
fine-grained Bazel test targets that can be tested incrementally.
There is work in progress for this, but it's not prioritized.
This commit additionally updates the Saucelabs test from iOS13
to iOS14 with a more recent emulator.. hopeing for better specs
of the Saucelabs VM and emulator.
0 commit comments