Noticed this when running chrome_sync_shell_test_apk locally with sanitizers:
I 2.612s TimeoutThread-1-for-Thread-5 [host]> /usr/local/google/home/agrieve/ssd/git/clankium1/src/third_party/android_tools/sdk/platform-tools/adb -s 0cd8b4bd02e47974 push /usr/local/google/home/agrieve/ssd/git/clankium1/src/tools/valgrind/asan/asan_symbolize.py /storage/emulated/legacy/chromium_tests_root/tools/valgrind/asan/asan_symbolize.py
I 2.643s TimeoutThread-1-for-Thread-5 [host]> /usr/local/google/home/agrieve/ssd/git/clankium1/src/third_party/android_tools/sdk/platform-tools/adb -s 0cd8b4bd02e47974 push /usr/local/google/home/agrieve/ssd/git/clankium1/src/tools/valgrind/asan/third_party/README.chromium /storage/emulated/legacy/chromium_tests_root/tools/valgrind/asan/third_party/README.chromium
I 2.681s TimeoutThread-1-for-Thread-5 [host]> /usr/local/google/home/agrieve/ssd/git/clankium1/src/third_party/android_tools/sdk/platform-tools/adb -s 0cd8b4bd02e47974 push /usr/local/google/home/agrieve/ssd/git/clankium1/src/tools/valgrind/asan/third_party/asan_symbolize.py /storage/emulated/legacy/chromium_tests_root/tools/valgrind/asan/third_party/asan_symbolize.py
I 2.713s TimeoutThread-1-for-Thread-5 [host]> /usr/local/google/home/agrieve/ssd/git/clankium1/src/third_party/android_tools/sdk/platform-tools/adb -s 0cd8b4bd02e47974 push /usr/local/google/home/agrieve/ssd/git/clankium1/src/tools/valgrind/asan/third_party/__init__.py /storage/emulated/legacy/chromium_tests_root/tools/valgrind/asan/third_party/__init__.py
I 2.748s TimeoutThread-1-for-Thread-5 [host]> /usr/local/google/home/agrieve/ssd/git/clankium1/src/third_party/android_tools/sdk/platform-tools/adb -s 0cd8b4bd02e47974 push /usr/local/google/home/agrieve/ssd/git/clankium1/src/third_party/llvm-build/Release+Asserts/bin/llvm-symbolizer /storage/emulated/legacy/chromium_tests_root/third_party/llvm-build/Release+Asserts/bin/llvm-symbolizer
I 3.724s TimeoutThread-1-for-Thread-5 [host]> /usr/local/google/home/agrieve/ssd/git/clankium1/src/third_party/android_tools/sdk/platform-tools/adb -s 0cd8b4bd02e47974 push /usr/local/google/home/agrieve/ssd/git/clankium1/src/tools/valgrind/asan/asan_symbolize.py /storage/emulated/legacy/chromium_tests_root/tools/valgrind/asan/asan_symbolize.py
I 3.774s TimeoutThread-1-for-Thread-5 [host]> /usr/local/google/home/agrieve/ssd/git/clankium1/src/third_party/android_tools/sdk/platform-tools/adb -s 0cd8b4bd02e47974 push /usr/local/google/home/agrieve/ssd/git/clankium1/src/tools/valgrind/asan/third_party/README.chromium /storage/emulated/legacy/chromium_tests_root/tools/valgrind/asan/third_party/README.chromium
I 3.824s TimeoutThread-1-for-Thread-5 [host]> /usr/local/google/home/agrieve/ssd/git/clankium1/src/third_party/android_tools/sdk/platform-tools/adb -s 0cd8b4bd02e47974 push /usr/local/google/home/agrieve/ssd/git/clankium1/src/tools/valgrind/asan/third_party/asan_symbolize.py /storage/emulated/legacy/chromium_tests_root/tools/valgrind/asan/third_party/asan_symbolize.py
I 3.878s TimeoutThread-1-for-Thread-5 [host]> /usr/local/google/home/agrieve/ssd/git/clankium1/src/third_party/android_tools/sdk/platform-tools/adb -s 0cd8b4bd02e47974 push /usr/local/google/home/agrieve/ssd/git/clankium1/src/tools/valgrind/asan/third_party/__init__.py /storage/emulated/legacy/chromium_tests_root/tools/valgrind/asan/third_party/__init__.py
I 3.933s TimeoutThread-1-for-Thread-5 [host]> /usr/local/google/home/agrieve/ssd/git/clankium1/src/third_party/android_tools/sdk/platform-tools/adb -s 0cd8b4bd02e47974 push /usr/local/google/home/agrieve/ssd/git/clankium1/src/third_party/llvm-build/Release+Asserts/bin/llvm-symbolizer /storage/emulated/legacy/chromium_tests_root/third_party/llvm-build/Release+Asserts/bin/llvm-symbolizer
We presumably don't need these host scripts / binaries on device.