[CI] Downgrade Maestro to 1.33.1 to fix timeouts #27034
Merged
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
tsapeta
force-pushed
the
@tsapeta/ci/downgrade-maestro
branch
from
9b0ce87
to
e9dec35
Compare
tsapeta
changed the title
alanjhughes
approved these changes
Feb 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
test-suite/ios-test job was hitting this issue: mobile-dev-inc/maestro#1585
We always used the latest version of Maestro, which is probably not a good idea. Let's pin to a specific version.
How
Since the issue refers to version
1.34.1, I tried1.34.0first, but it seems to be broken too. When I downgraded to1.33.1, the job passed twice.Test Plan
The job passed twice
Nightly tests are still failing, but this is different and unrelated issue.