ci: Address stalling Android E2E test tasks #66771
Conversation
dcalhoun
added
[Type] Automated Testing
dcalhoun
changed the title
Avoid erroneous cache hits that may result in the CI task hanging indefinitely while terminating the emulator.
This reverts commit 2e892a6.
Attempt to resolve indefinitely hanging Android E2E test tasks.
This reverts commit a4c844d.
AVD cache disabled as it caused emulator termination to hang indefinitely.
dcalhoun
force-pushed
the
ci/address-stalling-android-e2e-test-task
branch
from
c5df543 to
cfa7b81
Compare
|
Flaky tests detected in cfa7b81. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/11692403211
|
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
* ci: Increase AVD cache key specificity Avoid erroneous cache hits that may result in the CI task hanging indefinitely while terminating the emulator. * Revert "ci: Increase AVD cache key specificity" This reverts commit 2e892a6. * ci: Update Android test runner to macOS 13 Attempt to resolve indefinitely hanging Android E2E test tasks. * Revert "ci: Update Android test runner to macOS 13" This reverts commit a4c844d. * ci: Disable AVD cache AVD cache disabled as it caused emulator termination to hang indefinitely. Co-authored-by: dcalhoun <dpcalhoun@git.wordpress.org> Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
What?
Address recently indefinite hanging that occurs while terminating the emulator for the Android end-to-end test CI tasks.
Why?
The CI tasks never complete, so a successful test suite run is never reported, which blocks the pull request status and causes confusion.
How?
Remove the recommended AVD cache, as it appears its presence can cause indefinite hangs while terminating the emulator, as referenced several times in the
reactivecircus/android-emulator-runnerissue tracker:It is possible that removing the AVD cache is somewhat of an ineffective fix—temporarily solving the issue in the form of removing a problematic cache—but, given numerous other people report the AVD cache as problematic, I figure removing the AVD cache is worth a try.
Testing Instructions
N/A, no user-facing changes.
Testing Instructions for Keyboard
N/A, no user-facing changes.
Screenshots or screencast
N/A, no user-facing changes.