chore: capture adb logcat during e2e test retries#7341
Merged
janicduplessis merged 1 commit intodevelopfrom Apr 14, 2026
Merged
chore: capture adb logcat during e2e test retries#7341janicduplessis merged 1 commit intodevelopfrom
janicduplessis merged 1 commit intodevelopfrom
Conversation
Capture device logs via adb logcat alongside screen recordings when e2e tests fail and retry. Logs are saved as logcat.txt in the test artifacts directory for easier debugging.
|
π§ͺ Flashlight Performance Report (AWS Device Farm) π Commit: 81a1d98 π View Artifacts
|
olerass
approved these changes
Apr 14, 2026
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
2 participants
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.
Fixes APP-3626
What changed (plus any additional context for devs)
Extracted from the new arch migration PR #6924.
Adds adb logcat capture to the e2e test runner alongside screen recordings. When an Android e2e test fails and retries, device logs are now captured to
logcat.txtin the test artifacts directory. This makes it much easier to debug Android test failures, especially during the new arch migration where native crashes and warnings are common.The logcat capture starts/stops alongside screen recordings (on retry after first failure) and is also cleaned up in the emergency cleanup handler.
What to test