Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The `legacy-unit-tests-saucelabs` CI job is flaky

See original GitHub issue

The legacy-unit-tests-saucelabs CI job started to be quite flaky recently (no exact date, but roughly a few weeks ago). Based on today’s (04/29/2021) 10 commits to the master branch, that CI job failed 3 times (30% rate). Here is a link to the most recent failure. Curious if there is anything we can do (like reduce the number of concurrent connections, etc) or this is on the Saucelabs side?

// cc @josephperrott @devversion

Issue Analytics

State:
Created 2 years ago
Reactions:1
Comments:10 (9 by maintainers)

Top GitHub Comments

1reaction

AndrewKushnircommented, Apr 30, 2021

Yeah, also worth noting: I’m working on a proof of concept that allows us to run all individual Bazel karma_web_test_suite targets on Saucelabs (with the goal of removing the legacy job here; and in the components repository).

This is great! I guess that would also allow us to do retries on failures (with Bazel)? If yes, that’d really improve the situation.

1reaction

AndrewKushnircommented, Apr 30, 2021

We have a couple monitoring jobs that we run nightly that also use Saucelabs:

https://github.com/angular/angular/blob/master/.circleci/config.yml#L348-L393

I’m curious if it might be ok to run legacy-unit-tests-saucelabs jobs nightly too (instead of running for each PR)…