Android test running in VM does not include logcat file, but running same test outside VM generates it |
||
Issue descriptionAndroid test running in VM does not include logcat file, but running same test outside VM generates it Example: Builder: https://uberchromegw.corp.google.com/i/chromeos/builders/cyan-chrome-pfq/builds/903 On that builder page, there are links to both chromeos-image-archive and chromeos-autotest-results google storage locations (ie, the android.core.tests.libcore.package.harmony_java_math link under VMTest goes to chromeos-image-archive and the same label under HWTest goes to chromeos-autotest-results). The 'logcat' file is only in one of them, ie, $ gsutil -m cp -r gs://chromeos-image-archive/cyan-chrome-pfq/R59-9374.0.0-rc2/vm_test_results_1/test_harness/all/SimpleTestVerify/1_autotest_tests/results-02-cheets_CTS.6.0_r16.arm.android.core.tests.libcore.package.harmony_java_math . $ gsutil -m cp -r gs://chromeos-autotest-results/107192221-chromeos-test/chromeos4-row11-rack10-host13/ . $ find . -name logcat The logcat file only shows up in the chromeos-autotest-results archive (the chromeos4-row6-rack9-host19 folder).
,
Aug 1
,
Sep 28
Triage nag: This Chrome OS bug has an owner but no component. Please add a component so that this can be tracked by the relevant team.
,
Nov 8
<UI triage> Bug owners, please add the appropriate component to your bug. Thanks! |
||
►
Sign in to add a comment |
||
Comment 1 by aut...@google.com
, Apr 4 2017Owner: itspeter@chromium.org