As additional data points, both#1121 and#1122 timed out after 6 hours.

I've re-forked the repository and re-opened them as#1128 and#1127 to give them a chance to re-run.

Is this branch still viable as a solution?

After more investigation, I believe the issue is that forksdo not inherit repository secrets:

With the exception of GITHUB_TOKEN, secrets are not passed to the runner when a workflow is triggered from a forked repository.

This means that contributors submitting pull requests are executing their own suites in their own CI environments withoutaccess toSAUCE_USERNAME orSAUCE_ACCESS_KEY.

Do contributors need to register their own accounts and get their own secrets?

Do contributors need to register their own accounts and get their own secrets?

Ugh, that's quite a hurdle for contributing. Ideally we would run the tests from the GitHub actions instance ifSAUCE_KEY is not present, and use Sauce Labs only on PRs. Running the tests locally is much more reliable than CI.

But there must be something else going on. The test randomly fail some times even when theSAUCE_KEY is present. Not sure exactly why, but the error messages look like connection problems.

@seanpdoyle I've updated the CI script to only run tests on SauceLabs if it has access to anSAUCE_ACCESS_KEY.

#1130