betty-arcnext-pre-cq has been failing frequently lately in VMTest, with failures in login_VMSanity and cheets_ContainerSmokeTest_P: http://cros-goldeneye/chromeos/legoland/builderHistory?buildConfig=betty-arcnext-pre-cq&buildBranch=master

betty-pre-cq is fine, so the problem is presumably in the new ARC code: http://cros-goldeneye/chromeos/legoland/builderHistory?buildConfig=betty-pre-cq&buildBranch=master

Looking back a few days, the first failure I see is http://cros-goldeneye/chromeos/healthmonitoring/buildDetails?buildbucketId=8927174359096538784, started at 2018-12-14 01:44.

Here are some not very helpful errors:

12/14 06:06:26.106 ERROR|             utils:0287| [stderr] core/adb/adb_auth_host.c::generate_key():generate_key '/tmp/adb_keys/test_key'
12/14 06:06:26.430 ERROR|             utils:0287| [stderr] core/adb/adb_auth_host.c::write_public_keyfile():Writing public key to '/tmp/adb_keys/test_key.pub'
12/14 06:07:20.036 ERROR|             utils:2770| Timed out waiting for condition: Android container still running after Chrome shutdown.
12/14 06:07:23.026 ERROR|          parallel:0026| child process failed

...
12/14 06:11:07.221 INFO |        arc_common:0091| Waiting for Android to boot completely.
12/14 06:11:17.671 INFO |        arc_common:0107| Android has booted completely.
12/14 06:11:17.674 INFO |               arc:0837| Starting ARC setup
12/14 06:11:17.913 WARNI|              test:0606| The test failed with the following exception
Traceback (most recent call last):
  File "/usr/local/autotest/common_lib/test.py", line 567, in _exec
    _cherry_pick_call(self.initialize, *args, **dargs)
  File "/usr/local/autotest/common_lib/test.py", line 715, in _cherry_pick_call
    return func(*p_args, **p_dargs)
  File "/usr/local/autotest/common_lib/cros/arc.py", line 741, in initialize
    raise error.TestFail(err)
TestFail: Command <adb shell 'settings put global verifier_verify_adb_installs 0'> failed, rc=255, Command returned non-zero exit status
* Command: 
    adb shell 'settings put global verifier_verify_adb_installs 0'

It looks like it's failing more than half the time now, so I'm going to mark the builder experimental.