New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 823379 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

betty-arc64-nyc-android-pfq failing due to crostestutils.au_test_harness.au_test.AUTest timeout

Project Member Reported by sha...@chromium.org, Mar 19 2018

Issue description

Failing 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.
 
Cc: jhorwich@chromium.org kroot@chromium.org victorhsieh@chromium.org
Components: Platform>ARC
Labels: ArcConstable OS-Chrome
Owner: domlasko...@chromium.org
Status: Assigned (was: Untriaged)
Cc: norvez@chromium.org
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).

Comment 3 by gwendal@google.com, 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?

Status: Fixed (was: Assigned)
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