betty-arc64-nyc-android-pfq failing due to crostestutils.au_test_harness.au_test.AUTest timeout |
|||
Issue descriptionFailing repeatedly since 3/14: https://luci-milo.appspot.com/buildbot/chromeos/betty-arc64-nyc-android-pfq/ https://luci-milo.appspot.com/buildbot/chromeos/betty-arc64-nyc-android-pfq/901 TimeoutError: Timeout occurred- waited 3600.0 seconds. Reached VMTestStage test run timeout. I don't see anything helpful in the test_harness artifacts.
,
Mar 19 2018
My last finding last week was that when I cros flash betty-arc64/R67-10490.0.0, cheets_CTS_N.x86.CtsDramTestCases passed. But if I push the same version of Android prebuilt, it failed. It could be that changes by CrOS signer matter here (though it also could be that our push tool has some problem).
,
Mar 20 2018
betty ARC++ N turned back green. https://luci-milo.appspot.com/buildbot/chromeos/betty-arc64-nyc-android-pfq/905, can we update android-container-nyc to 4665220?
,
Mar 20 2018
The culprit was last week's Phonesky roll. It's still unclear why it does not play well with betty-arc64, but I assume jhorwich@ will investigate for the reland. gwendal: the PFQ should turn green soon now that crbug.com/823448 is fixed. |
|||
►
Sign in to add a comment |
|||
Comment 1 by domlasko...@chromium.org
, Mar 19 2018Components: Platform>ARC
Labels: ArcConstable OS-Chrome
Owner: domlasko...@chromium.org
Status: Assigned (was: Untriaged)