Use None
to signal adb
binary default for chrome_android
-related products
#33669
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.
The change #33654 caused
chrome_android
-related runs without--adb-binary
to fail because the corresponding kwarg wasNone
but present. Constructing the browser overwrote the kwarg default.This change fixes that bug by using
None
to signal defaultadb
usage.This time, I tested the change on the
run_monochrome_webview_finch_smoke_tests
target in Chromium as well, which does not pass--adb-binary
to wptrunner.