android-emulator-runner: Emulator crashing?
Hello there! First of all, congratulations on the work done on this great project. I am facing the following problem:
- Trying to run Android connected tests with the following configuration https://github.com/lz1asl/CaveSurvey/blob/fixes/.github/workflows/android.yml
- name: Connected tests uses: reactivecircus/android-emulator-runner@v2 with: api-level: 29 script: ./gradlew connectedAndroidTest
- They fail (for example https://github.com/lz1asl/CaveSurvey/runs/739356848?check_suite_focus=true) with
Task :connectedDefaultFlavorDebugAndroidTest Starting 12 tests on test(AVD) - 10 com.astoev.cave.survey.test.service.data.ExcelExportTest > excelExportTest[test(AVD) - 10] FAILED Test failed to run to completion. Reason: 'Test run failed to complete. Expected 12 tests, received 6'. Check device logcat for details Tests on test(AVD) - 10 failed: Test run failed to complete. Expected 12 tests, received 6. onError: commandError=false message=INSTRUMENTATION_ABORTED: System has crashed. > Task :connectedDefaultFlavorDebugAndroidTest FAILED
- As mentioned in other issues added logcat output https://github.com/lz1asl/CaveSurvey/runs/751427443?check_suite_focus=true and I see the crash
--------- beginning of crash 06-08 20:23:57.017 1590 1590 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 1590 (surfaceflinger), pid 1590 (surfaceflinger)
but am still not sure what is causing it. Do you think you can have a look? Same tests work fine locally.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 3
- Comments: 17 (6 by maintainers)
Filed an issue after an in-depth analysis of the problem.
https://issuetracker.google.com/issues/159732638
Firing the issue on the issuetracker will have a much better chance getting to the Emulator team who have been very responsive and helpful in my personal experience (sometimes they will even send you an unreleased emulator binary for you to try). If it’s a bug in the emulator binary or system images, those GitHub repos are completely irrelevant and the best they can do is firing the issue for you.
Closing now as no action can be taken on our side.
And its gone. The error is gone. I did nothing except adding 28 to my build matrix and the error is gone. I have been at this for 3-4 hours now. 😐