[Android] Adding debug logs - #5461
Draft
IvanBM18 wants to merge 26 commits into
Draft
Conversation
…seen" This reverts commit e61947c.
IvanBM18
force-pushed
the
feature/android-debug-logs
branch
from
September 8, 2026 17:44
b907e82 to
81e40db
Compare
IvanBM18
added a commit
that referenced
this pull request
Sep 11, 2026
Bug: b/553141628 ## Overview Since Android API level 30 (and apps targeting Android 11+), apps have scoped storage access. Previously, bad build checks for Android did not verify whether the application process actually survived startup because `am start` returns 0 even if the process dies immediately. This PR enhances `check_for_bad_build()` in `testcase_manager.py` by ensuring command line files are written prior to execution and flipping a conditional so in the bad build check the android specific validation proceeds other validations. The later was required because thanks to [this PR](733e28f?diff=unified) we added the possibility to check for false positives, but this added a problem in which valid builds were incorrectly flagged as crashes, so by flipping the conditional we fix this. ## Changes - `src/clusterfuzz/_internal/bot/testcase_manager.py`: Updated `check_for_bad_build()` to pass `write_command_line_file=True` and verify target application process presence on Android post-launch. ## Tests performed > Basically the same as the parent PR - Tested them in swarming: https://chrome-swarming.appspot.com/task?id=7a8188fe65a42510 - Tested them locally using an avd device against an invalid apk, that is the previous iteration of our chrome public apk, the apk returned the following: ``` reason=2 (SIGNALED) subreason=0 (UNKNOWN) status=9 ``` When this happen now CF correctly determines that the app crashed due to runtime issues not related to memory errors. ## PR stack - `master` - **#PR 2.1a** `feature/android-exit-code-constants` - **#PR 2.1b** `feature/android-exit-code-core` - **#PR 2.2** `feature/android-exit-code-process-handler` - **#PR 2.3** `feature/android-bad-build-check` 👈 ## Note: Adding additional debug logs in this other PR: - #5461
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
1 participant
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.
Overview
Adding debug level logs to follow android fuzzing sessions and interactions.
Changes
Basically changed the debug level for a ton of logs in android related functionality, i focused specifically at:
Note
This PR is dependent to 2 PRs coming from 2 different PR stacks: