Repository navigation
Android emulator tests: notice the emulator exiting, bound every wait, keep its log - #827
Merged
Merged
Conversation
…, keep its log The alpha125 release run sat in "Start the emulator" for 25 minutes: the emulator had exited (no emulator among the orphans at cleanup, only adb), and `adb wait-for-device` has no limit. The step now polls the emulator process and boot_completed with time limits, prints the emulator's log and the KVM state when it fails, and the job keeps emulator.log. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or 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
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.
Release run 43225036000 (alpha125, attempt 2) sat in Run Android tests → Start the emulator for 25 minutes until I cancelled it.
What happened
The step's log stops after
* daemon started successfully. At cleanup the runner killed two orphanadbprocesses but no emulator. So the emulator exited soon after it started, andadb wait-for-device, which has no time limit, waited for a device that would never come. Its reason is inemulator.log, which the job didn't print or keep.Change
Start the emulatornow:/dev/kvmandemulator -accel-checkfirst;/dev/null;sys.boot_completedunder a 10 stimeout. There is no unboundedwait-for-deviceany more;emulator.logand fails. After 10 minutes it printsadb devicesand the log's tail and fails.emulator.logis also uploaded with the results.Testing
This PR changes the workflow, so its own CI runs it against the newest published release's package. That run shows the real reason the emulator exits; a follow-up commit here fixes it.
🤖 Generated with Claude Code