LMKD is killing `androidx.test.services` during test runs
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java
- Domain
- mobile, testing-qa
Research direction
Start by reproducing the failure with ./gradlew connectedAndroidTest under low-memory conditions on Android 12, then inspect logcat for lmkd killing androidx.test.services. Review the listed AndroidX Test dependencies and confirm that connectedAndroidTest completes successfully without the instrumentation process crashing.
Written by the indexing model from the issue text.
Description
Description
connectedAndroidTest runs are failing with the error "Instrumentation run failed due to Process crashed." which is caused by the lmkd killing androidx.test.services to reclaim memory.
Steps to Reproduce
Need to create a low-memory situation and then run ./gradlew connectedAndroidTest
Expected Results
connectedAndroidTest runs and completes successfully
Actual Results
connectedAndroidTest runs, but fails after one or two tests with the error message: "Test run failed to complete. Instrumentation run failed due to Process crashed."
Inspecting logcat gives the following:
2023-01-30 15:17:46.821 483-483 lmkd lmkd I Reclaim 'androidx.test.services' (15979), uid 10272, oom_score_adj 200, state 4 to free 45252kB rss, 46040kb swap
AndroidX Test and Android OS Versions
Android OS: 12
Device: Samsung TabActive 3
'androidx.test:orchestrator:1.4.2'
'androidx.test🏃1.5.2'
'androidx.test:rules:1.5.0'
"androidx.test:monitor:1.6.1"
'androidx.test.ext:junit:1.1.5'
'androidx.test.espresso:espresso-core:3.5.1'
'androidx.test.uiautomator:uiautomator:2.2.0'
'androidx.navigation:navigation-testing:2.5.3'
Link to a public git repo demonstrating the problem:
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 342
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 5
Getting set up
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 android/android-test
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
android/android-test#681 · 2 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
android/android-test#2507 · 1 comment ·
-
ξεκσνδξδOpen
Difficulty 5/5 Over a week Newbie friendliness 1/100
android/android-test#2499 ·
-
ησξξσOpen
Difficulty 5/5 Over a week Newbie friendliness 1/100
android/android-test#2498 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
android/android-test#2473 ·
All issues in android/android-test
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
checkstyle/checkstyle#21755 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/copilot-sdk#2782 ·
Maintainers usually reply within 1 day
-
documentation Good for newcomer quick win
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CodeForPhilly/benefit-decision-toolkit#519 ·
Maintainers usually reply within 1 day
-
area-deployment triage:bot-seen triage:needs-human
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/aspire#20533 · 1 comment ·
Maintainers usually reply within 1 day