-
Notifications
You must be signed in to change notification settings - Fork 139
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
Fix flaky tests on CI #174
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
released
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Comments
arriolac
added
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
triage me
I really want to be triaged.
labels
Jul 12, 2022
Looks like there are 2 causes for the failed actions linked in the description:
|
This was referenced Jul 12, 2022
Merged
4 tasks
This was referenced Aug 18, 2022
wangela
added
priority: p2
Moderately-important priority. Fix may not be included in next release.
and removed
triage me
I really want to be triaged.
labels
Oct 21, 2022
This was referenced Jan 5, 2023
wangela
pushed a commit
that referenced
this issue
Jan 7, 2023
Tests cannot pass on PRs from forks. Root cause: community/community#50161 |
🎉 This issue has been resolved in version 2.11.4 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
released
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Steps to reproduce
Run the test workflow on
main
and notice that instrumentation tests are failing. Example failed runs:https://github.com/googlemaps/android-maps-compose/runs/7306842111
https://github.com/googlemaps/android-maps-compose/runs/7283340731
Also see discussion in #171
Code example
N/A
Stack trace
The text was updated successfully, but these errors were encountered: