Skip to content

build: increase timeout for legacy saucelabs tests #20029

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

devversion
Copy link
Member

We keep adding more tests to our codebase, but browsers
on Saucelabs generally run slow. During the last couple of
weeks unit tests on Saucelabs sometimes failed due to the default 10min
timeout. e.g. https://app.saucelabs.com/tests/bfb7ade4b0fc4e7e9ff7237074baac80

We bump the timeout so that tests can complete without us relaunching
another instance of a browser (which might pass; but will increase CI
duration even more). We use the maximum value of 1000seconds.

Ideally we'll fix this in the future by having incremental test runs.
I'm working on this with a Bazel setup as a side project. See:
#19409

We keep adding more tests to our codebase, but browsers
on Saucelabs generally run slow. During the last couple of
weeks unit tests on Saucelabs sometimes failed due to the default 10min
timeout. e.g. https://app.saucelabs.com/tests/bfb7ade4b0fc4e7e9ff7237074baac80

We bump the timeout so that tests can complete without us relaunching
another instance of a browser (which might pass; but will increase CI
duration even more). We use the maximum value of 1000seconds.

Ideally we'll fix this in the future by having incremental test runs.
I'm working on this with a Bazel setup as a side project. See:
angular#19409
@devversion devversion added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent merge safe target: patch This PR is targeted for the next patch release labels Jul 17, 2020
@devversion devversion requested a review from a team as a code owner July 17, 2020 16:41
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jul 17, 2020
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@crisbeto crisbeto added lgtm action: merge The PR is ready for merge by the caretaker labels Jul 17, 2020
@andrewseguin andrewseguin merged commit 80e4d3f into angular:master Jul 17, 2020
andrewseguin pushed a commit that referenced this pull request Jul 17, 2020
We keep adding more tests to our codebase, but browsers
on Saucelabs generally run slow. During the last couple of
weeks unit tests on Saucelabs sometimes failed due to the default 10min
timeout. e.g. https://app.saucelabs.com/tests/bfb7ade4b0fc4e7e9ff7237074baac80

We bump the timeout so that tests can complete without us relaunching
another instance of a browser (which might pass; but will increase CI
duration even more). We use the maximum value of 1000seconds.

Ideally we'll fix this in the future by having incremental test runs.
I'm working on this with a Bazel setup as a side project. See:
#19409

(cherry picked from commit 80e4d3f)
ngwattcos pushed a commit to ngwattcos/components that referenced this pull request Jul 20, 2020
We keep adding more tests to our codebase, but browsers
on Saucelabs generally run slow. During the last couple of
weeks unit tests on Saucelabs sometimes failed due to the default 10min
timeout. e.g. https://app.saucelabs.com/tests/bfb7ade4b0fc4e7e9ff7237074baac80

We bump the timeout so that tests can complete without us relaunching
another instance of a browser (which might pass; but will increase CI
duration even more). We use the maximum value of 1000seconds.

Ideally we'll fix this in the future by having incremental test runs.
I'm working on this with a Bazel setup as a side project. See:
angular#19409
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Aug 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants