ci: downgrade to sauce-connect v4.5.1 - #28659
Closed
devversion wants to merge 1 commit into
Closed
Conversation
We currently face a lot of flakiness with our Saucelabs CI jobs. These randomly exceed the 10min CircleCI no-output limit because something throws off `sauce-connect` in a long-lasting loop where it tries to connect to some of their Saucelabs servers. The initial assumption from the Saucelabs team was that we might have some invalid firewall rules, but this does not answer why this happens _randomly_, so the latest update from the support is that there have been some changes in the latest version of `sauce-connect` version that **could** cause this flakiness. I've manually did multiple test runs and was only able to reproduce the issues with v4.5.3 (latest version), so it might be worth downgrading to v4.5.1. This is also what the Saucelabs support proposed us to do (though it's not guaranteed that v4.5.1 is unaffected by the same issue)
devversion
force-pushed
the
build/downgrade-sauce-connect-v4.5.1
branch
from
February 12, 2019 17:58
5942b26 to
6e6c87d
Compare
devversion
added
area: build & ci
IgorMinar
approved these changes
Feb 12, 2019
IgorMinar
added
action: merge
mhevery
pushed a commit
that referenced
this pull request
Feb 13, 2019
We currently face a lot of flakiness with our Saucelabs CI jobs. These randomly exceed the 10min CircleCI no-output limit because something throws off `sauce-connect` in a long-lasting loop where it tries to connect to some of their Saucelabs servers. The initial assumption from the Saucelabs team was that we might have some invalid firewall rules, but this does not answer why this happens _randomly_, so the latest update from the support is that there have been some changes in the latest version of `sauce-connect` version that **could** cause this flakiness. I've manually did multiple test runs and was only able to reproduce the issues with v4.5.3 (latest version), so it might be worth downgrading to v4.5.1. This is also what the Saucelabs support proposed us to do (though it's not guaranteed that v4.5.1 is unaffected by the same issue) PR Close #28659
|
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. |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
6 participants
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.
We currently face a lot of flakiness with our Saucelabs CI jobs.
These randomly exceed the 10min CircleCI no-output limit because
something throws off
sauce-connectin a long-lasting loop whereit tries to connect to some of their Saucelabs servers. The initial
assumption from the Saucelabs team was that we might have some
invalid firewall rules, but this does not answer why this happens
randomly, so the latest update from the support is that there have
been some changes in the latest version of
sauce-connectversion thatcould cause this flakiness.
I've manually did multiple test runs and was only able to reproduce the issues
with v4.5.3 (latest version), so it might be worth downgrading to v4.5.1. This is
also what the Saucelabs support proposed us to do (though it's not guaranteed
that v4.5.1 is unaffected by the same issue)