wonderfly@, Can you check since logs show you as the most active contributor to SimpleTestVerify test called.

I will be more than happy to help but won't have the bandwidth as a primary owner. I too haven't touched that code for a while. Besides, my brief look seems to suggest the test performed an AutoUpdate and then was not able to connect to the updated test instance. So more likely an image issue than an infra one.

I forced all packages to be built with gcc but the test still failed.
https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/chromium_pfq/builds/24

Btw, the test passed when I ran it locally adding to the confusion. 

Note that the VMTest test passes on falco and the compiler generates same code for both. So it should not be a compiler error but maybe a QEMU/Test issue.

Attaching cpu flags information for falco/squawks and my goobuntu desktop.

Deleted: falco_cpuflags.txt 1.9 KB

falco_cpuflags.txt 1.9 KB View Download

Deleted: squawks_cpuflags.txt 1.8 KB

squawks_cpuflags.txt 1.8 KB View Download

Deleted: goobuntu_cpuflags.txt 48.0 KB

goobuntu_cpuflags.txt 48.0 KB View Download

wonderfly@, Would appreciate any help in how to debug. The current set of logs aren't very helpful.

Looking the logs here:

https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/release/builds/9348/steps/VMTest%20%28attempt%201%29/logs/stdio

Seems like error is regarding no disk space left when trying to do an update in VM.

14:50:18: ERROR: Failed to perform stateful partition update: return code: 1; command: ssh -p 52894 '-oConnectionAttempts=4' '-oUserKnownHostsFile=/dev/null' '-oProtocol=2' '-oConnectTimeout=30' '-oServerAliveCountMax=3' '-oStrictHostKeyChecking=no' '-oServerAliveInterval=10' '-oNumberOfPasswordPrompts=0' '-oIdentitiesOnly=yes' -i /tmp/cbuildbot-tmp4lHSc5/ssh-tmpk_GrOe/testing_rsa root@localhost -- sh /mnt/stateful_partition/cros-flash/tmp.b5XM6bE4Qz/stateful_update /mnt/stateful_partition/cros-flash/tmp.b5XM6bE4Qz/stateful.tgz
Warning: Permanently added '[localhost]:52894' (RSA) to the list of known hosts.
Reading local payload /mnt/stateful_partition/cros-flash/tmp.b5XM6bE4Qz/stateful.tgz
tar: dev_image_new/telemetry/src/third_party/catapult/third_party/vinn/third_party/v8/linux/x86_64/d8: Wrote only 7680 of 10240 bytes
tar: dev_image_new/telemetry/src/third_party/catapult/third_party/vinn/third_party/v8/LICENSE.v8: Cannot write: No space left on device

jrbarnette@, Do you know who can take a look at the VMTest test issues. It looks like VM is running out of space.

To get help from the CrOS Infra team on a bug, use
component Infra>Client>ChromeOS.

To get urgent help, you should also copy the primary
and secondary deputies for the week; see
go/cros-infra-deputy for who that is.

+ deputy 

It failed on caroline-release too.

https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/release/builds/9356

But in the waterfall, the caroline-release does not have vmtest, the vmtest only happens on trybot, is this expected?

I saw a change to increase disk space to address failing VMTest https://chromium-review.googlesource.com/c/450979 . I hope this will also fix squawks issue.

Looks like a duplicate of Issue 692206. After Mar 7 no errors are reported again.