ci: update saucelabs protractor config to run e2e tests in series rather than parallel #15545
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…her than parallel
josephperrott
added
area: etc/misc
target: major
|
@josephperrott any reason why we should not backport this to patch branch? |
clydin
approved these changes
Sep 6, 2019
|
@alan-agius4 no, I suppose that we should be able to run it on any branch. Will update label |
josephperrott
added
target: patch
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our combined CI usage is often hitting the max number of concurrent sessions on saucelabs. Currentl the saucelabs job takes 12 sessions at once because the tests run in parallel, instead we should run these in series to only use 1 session.
It should not have a large impact on overall CI run time as each of the tests take ~10 seconds so we are moving from the Saucelabs steps taking ~1:45 to ~3:00 each. Based on previous CI runs it looks like this change will still cause the saucelabs test runs to complete ~15 minutes before other jobs in the sequence.