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

Issue 885186 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Sep 18
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

betty-arcnext CQ and PFQ failing in cheets_CTS_P.9.0_r3.arm.CtsAccountManagerTestCases

Project Member Reported by steve...@chromium.org, Sep 18

Issue description

Output snippet:
21:04:45 INFO | autoserv| [stdout] 09-18 04:04:45 D/ModuleListener: ModuleListener.testStarted(android.accounts.cts.AccountManagerTest#testConfirmCredentialsAccountNotOnDevice)
21:05:18 INFO | autoserv| [stdout] 09-18 04:05:18 D/InstrumentationResultParser: unrecognized line INSTRUMENTATION_ABORTED: System has crashed.
21:05:18 INFO | autoserv| [stdout] 09-18 04:05:18 I/InstrumentationResultParser: test run failed: 'Test run failed to complete. Expected 151 tests, received 21'

Cc: kinaba@chromium.org
Owner: kinaba@chromium.org
Status: Fixed (was: Untriaged)
> Test failed due to Failed: Not all tests were executed. After 1 retries passing 151 tests, waived=0. run(p=150, f=1, w=0) retry(p=151, f=0, w=0).

They are both b/115944638, which I have landed a fix already.
https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/1229814



The test became unintentionally strict and upright on system crash, and I basically added back to ignore random ARC crashes as much as possible, as before my change few days ago.

So basically, the current state is just re-hiding a lot of real bugs.
That's also concerning and I started a bit of categorization of found crashes in b/115944638.


Any way, this particular test's failure should be fixed now. 
Cool thanks!

Issue 885199 has been merged into this issue.

Sign in to add a comment