-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Flaky instrumented tests #10998
Comments
Adding here that I'm seeing the following issue lately:
While this doesn't originate from a flaky test, it does make our CI unreliable. |
got another one 😒 https://circleci.com/gh/mapbox/mapbox-gl-native/67704?utm_campaign=build-failed&utm_medium=email&utm_source=notification I don't have the permissions to look at the output in firebase.
|
Saw this failure on #11442:
|
Unclear to me why, but this build on |
This
|
This
|
This
|
Appears to be identical to @mollymerp 's: https://circleci.com/gh/mapbox/mapbox-gl-native/99095
If you have Firebase permissions more details are available... |
This |
Apologies for not being able to fix/prioritize this. Just looked at the impact of the issue and seeing 4 out of 100 builds failing. I feel this is on par with stability of the other integrations. Will try to find some bandwidth to look more into this issue. |
Capturing from @friedbunny and @1ec5 that they have noticed flaky executions of the test suite on Firebase testlab. This issue has additional background in #3539. Note that these tests have been running reliable since #10333.
Impact
To quantify the impact, 8 out of 100 firebase executions are suffering from this issue. The first mention of the tests being flaky goes back to Thursday, 01-18-2018.
Example of a failed test
The corresponding video is showing that we weren't able to load the map. In other words, the OnMapReady callback wasn't invoked before the OnIdleResource timed out.
The text was updated successfully, but these errors were encountered: