Tracking Mobile E2E failures on Github Action CI

[cameronvoell]

Describe the bug Following the Monorepo effort for making the native mobile version of Gutenberg available in the gutenberg repo, we added Android and iOS Github actions to continuous integration on pull requests for catching issues.

This Issue is for tracking any (hopefully rare) randomly occurring issues on those CI jobs so that the tests are reliable. If you see a failure on a mobile E2E test that is not related to changes in a PR, please add a comment below.

If known random failures that occur a meaninful amount of time are all fixed, this issue will be closed and any future issues can be resolved individually.

Link to recent Android Failures: https://github.com/WordPress/gutenberg/actions?query=workflow%3A%22React+Native+E2E+Tests+%28Android%29%22+is%3Afailure

Link to recent iOS Failures: https://github.com/WordPress/gutenberg/actions?query=workflow%3A%22React+Native+E2E+Tests+%28iOS%29%22+is%3Afailure

[jordesign]

Checking through some older issues and wanted to check if this is still relevant?

[guarani]

👋 @dcalhoun, do you happen to have an answer to this one? I'm no longer on this project but I'm still subscribed to this issue. @\cameronvoell isn't working on this anymore either.

[dcalhoun]

Thanks for the ping, @Guarani.

My perception is that no one actively considers this issue or its focus. Therefore, I do not believe its presence brings value and I closed it. If anyone disagrees, please feel free to reopen the issue.

@WordPress/native-mobile moving forward, we could consider automating flaky test tracking, similar to the web project's packages/report-flaky-tests.