Improve emulator lifecycle reliability (boot/cpu/animation exception handling)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- android, csharp
- Domain
- mobile-dev, tooling
Research direction
Start in Emulator.cs with WaitForBootComplete, WaitForCpuLoadBelow, and DisableAnimations, then review the existing retry behavior in FindRunningEmulatorSerialByAvdName. Run the current tests and add coverage for DisableAnimations and launcher waiting in WaitForBootComplete. Done means transient ADB failures are handled as described and the unused System.Data import is removed.
Written by the indexing model from the issue text.
Description
Ref: PR #63
The following improvements were identified during review of PR #63 to improve reliability and handle transient ADB failures:
- WaitForBootComplete: The
adb.Shellcalls inside the polling loop (lines ~355) can throwSdkToolFailedExitExceptionif adb exits non-zero. These should be wrapped in atry-catchblock to allow retrying, similar toFindRunningEmulatorSerialByAvdName. - WaitForCpuLoadBelow: The
adb.Shellcall (line ~401) should also be wrapped intry-catchto handle transient failures. - DisableAnimations: The
adb.Shellcalls (line ~429) should be best-effort and wrapped intry-catch. - Test Coverage: Add tests for
DisableAnimationsand the new launcher waiting logic inWaitForBootComplete. - Cleanup: Remove unused
using System.Data;inEmulator.cs.
- Dominant language
- C#
- Stars
- 78
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Redth/AndroidSdk.Tools
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
Redth/AndroidSdk.Tools#85 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
Redth/AndroidSdk.Tools#84 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Redth/AndroidSdk.Tools#66 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
Redth/AndroidSdk.Tools#64 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Redth/AndroidSdk.Tools#41 ·
All issues in Redth/AndroidSdk.Tools
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·