This was the test run: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8927250955486207232

I just tried some of these tests and they passed.

Previous run had 5 failures:
https://storage.cloud.google.com/chromeos-image-archive/amd64-generic-telemetry/R73-11395.0.0-b3224433/vm_test_results_1/telemetry_unit_server/test_harness/all/SimpleTestVerify/1_autotest_tests/results-1-telemetry_UnitTestsServer/telemetry_UnitTestsServer.user/debug/client.0.DEBUG

telemetry.page.page_run_end_to_end_unittest.ActualPageRunEndToEndTests.testSharedPageStateCannotRunOnBrowser
telemetry.core.tracing_controller_unittest.TracingControllerTest.testExceptionRaisedInStopTracing
telemetry.core.tracing_controller_unittest.TracingControllerTest.testFlushTracing
telemetry.core.tracing_controller_unittest.TracingControllerTest.testGotTrace
telemetry.core.tracing_controller_unittest.TracingControllerTest.testStartAndStopTraceMultipleTimes

Same stack, so tests are randomly failing on startup.

The run before that:
https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8927295635130458272
log:
https://storage.cloud.google.com/chromeos-image-archive/amd64-generic-telemetry/R73-11393.0.0-b3223150/vm_test_results_1/telemetry_unit_server/test_harness/all/SimpleTestVerify/1_autotest_tests/results-1-telemetry_UnitTestsServer/telemetry_UnitTestsServer.user/debug/client.0.log

This had 16 failures. Each failure takes times out after 4 min, so these 16 failures consume more than an hour, which is why the second VMTest run times out.

The 16 failing tests:
telemetry.internal.backends.chrome_inspector.inspector_runtime_unittest.InspectorRuntimeTest.testRuntimeEvaluateOfSomethingThatCantJSONize
telemetry.internal.browser.extension_unittest.MultipleExtensionTest.testExtensionGetByExtensionId
telemetry.internal.browser.extension_unittest.MultipleExtensionTest.testWebApp
telemetry.internal.browser.extension_unittest.NonExistentExtensionTest.testExtensionBasic
telemetry.internal.browser.extension_unittest.NonExistentExtensionTest.testExtensionGetByExtensionId
telemetry.internal.browser.extension_unittest.NonExistentExtensionTest.testExtensionNotLoaded
telemetry.internal.browser.extension_unittest.NonExistentExtensionTest.testWebApp
telemetry.internal.browser.extension_unittest.WebviewInExtensionTest.testExtensionBasic
telemetry.internal.browser.extension_unittest.WebviewInExtensionTest.testExtensionGetByExtensionId
telemetry.internal.browser.extension_unittest.WebviewInExtensionTest.testWebApp
telemetry.internal.browser.tab_unittest.ServiceWorkerTabTest.testClearDataForOrigin
telemetry.internal.browser.tab_unittest.ServiceWorkerTabTest.testIsServiceWorkerActivatedOrNotRegistered
telemetry.internal.browser.tab_unittest.TabTest.testActivateTab
telemetry.internal.browser.tab_unittest.TabTest.testGetFirstRendererThread_multipleTabs
telemetry.internal.browser.tab_unittest.TabTest.testGetFirstRendererThread_singleTab
telemetry.internal.browser.tab_unittest.TabTest.testIsVideoCaptureRunning

looks like the bot has database failure due to space issue.

chrome log from last successful test.
------------
[9072:9072:1214/160141.003410:VERBOSE1:webui_login_view.cc(595)] Login WebUI >> login-prompt-visible
[9072:9072:1214/160141.044730:WARNING:server_backed_state_keys_broker.cc(75)] Failed to obtain server-backed state keys.
[9072:9072:1214/160142.061463:WARNING:CONSOLE(2651)] "Could not find style data in module named", source: chrome://resources/polymer/v1_0/polymer/polymer-extracted.js (2651)
[9072:9094:1214/160142.196728:WARNING:value_store_frontend.cc(44)] Reading iadeocfgjdjdmpenejdbfeaocpbikmab.alarms from  failed: IO error: .../MANIFEST-000347: FILE_ERROR_NO_SPACE (ChromeMethodBFE: 3::WritableFileAppend::8)
[9072:9094:1214/160142.203384:WARNING:value_store_frontend.cc(44)] Reading mppnpdlheglhdfmldimlhpnegondlapf.alarms from  failed: IO error: .../MANIFEST-000347: FILE_ERROR_NO_SPACE (ChromeMethodBFE: 3::WritableFileAppend::8)
[9072:9094:1214/160142.209677:WARNING:value_store_frontend.cc(44)] Reading mhjfbmdgcfjbbpaeojofohoefgiehjai.alarms from  failed: IO error: .../MANIFEST-000347: FILE_ERROR_NO_SPACE (ChromeMethodBFE: 3::WritableFileAppend::8)
[9072:9094:1214/160142.216557:WARNING:value_store_frontend.cc(44)] Reading fgoepimhcoialccpbmpnnblemnepkkao.alarms from  failed: IO error: .../MANIFEST

next chrome log that failed
---------------------------

[9338:9398:1214/160529.574954:ERROR:data_store_impl.cc(131)] Failed to open Data Reduction Proxy DB: 3
[9338:9394:1214/160529.624360:ERROR:database.cc(1808)] Passwords sqlite error 13, errno 0: database or disk is full, sql: INSERT OR REPLACE INTO meta (key,value) VALUES (?,?)
[9338:9394:1214/160529.637915:ERROR:database.cc(1808)] Passwords sqlite error 13, errno 0: database or disk is full, sql: INSERT OR REPLACE INTO meta (key,value) VALUES (?,?)
[9338:9394:1214/160529.638549:ERROR:database.cc(1808)] Passwords sqlite error 1, errno 0: cannot commit - no transaction is active, sql: COMMIT
[9338:9394:1214/160529.638794:ERROR:login_database.cc(639)] Unable to commit a transaction.
[9338:9338:1214/160529.642945:VERBOSE1:drm_display_host_manager.cc(248)] Got display event ADD for /dev/dri/card1
[9338:9394:1214/160529.643441:ERROR:password_store_default.cc(41)] Could not create/open login database.


Should we increase the diskspace for VM?


I did find real failure: testActivateTab. I'll file a separate bug for it.

This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.