This test also consistently fails for snappy:

https://stainless.corp.google.com/search?exclude_cts=true&exclude_non_release=true&board=%5Esnappy%24&suite=%5Esecurity%24&view=matrix&col=build&row=test&first_date=2018-06-29&last_date=2018-07-26

This should be investigated/fixed.

It happened again on fizz.

https://stainless.corp.google.com/browse/chromeos-autotest-results/220645639-chromeos-test/

ping for owner for this bug.
Any

This continues to fail, and there is no owner.

assigning to Puthik since he is one of the people that have modified this test.
Please re-assign or fix.

and what is the appropriate component for this bug.

drewry@

Will, can you help find an owner for this issue. Thanks

This is happening quite regularly. Either somebody needs to fix this issue, or we need to disable this test.

Below are just the failures we've seen in the last week:

https://luci-logdog.appspot.com/v/?s=chromeos/buildbucket/cr-buildbucket.appspot.com/8934573430560381936/+/steps/HWTest__security_/0/stdout
https://luci-logdog.appspot.com/v/?s=chromeos/buildbucket/cr-buildbucket.appspot.com/8934935827252604224/+/steps/HWTest__security_/0/stdout
https://luci-logdog.appspot.com/v/?s=chromeos/buildbucket/cr-buildbucket.appspot.com/8935026416542473328/+/steps/HWTest__security_/0/stdout
https://luci-logdog.appspot.com/v/?s=chromeos/buildbucket/cr-buildbucket.appspot.com/8935298204715575200/+/steps/HWTest__security_/0/stdout


If you look at this test on Stainless, you will see many failures:

https://stainless.corp.google.com/search?test=%5Esecurity%5C_x86Registers$&first_date=2018-08-19&last_date=2018-09-16&row=model&col=build&view=matrix

I'm happy to take a look, though I don't know whether I have a fizz device handy to test things locally. Can someone plug in a fizz device and paste the IP address here?

If it's easier for you to find one, it also fails pretty consistently on snappy, caroline, pyro, relm, terra and ultima.

I do have a caroline.

(not sure if this is the cause for all errors)

it looks like this logic needs updating for some newer CPUs? (like cave?)

https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/client/cros/power/power_utils.py?type=cs&q=power_utils+get_x86_cpu_arch&g=0&l=29

an example of not recognized CPU for cave

https://cmtice.users.x20web.corp.google.com/www/tt_cave_x86Registers.v2.out

I can def repro the failures, looking at the best short-term workaround for this.

Oh, and I should say: TestNA should not be considered an error -- on this test, for example, TestNA makes sense for ARM devices.

soraka, and caroline, on the other hand, are proper failures.

Fix is at https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/1259564

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/f0ea56d4f6c8f439b047159694e890a40ce89fef

commit f0ea56d4f6c8f439b047159694e890a40ce89fef
Author: Jorge Lucangeli Obes <jorgelo@google.com>
Date: Fri Oct 05 14:21:50 2018

security_x86Registers: Fix VMX-related failures.

This test might not be long for this world. It tests VMX state in the
corresponding MSR, and the BILD bit in firmware. Well, it turns out VMX
is being set in all the boards supporting Crostini, so that check is
not very useful anymore.

Remove the VMX check on Intel for now, but keep the BILD check, which
is still useful.

BUG= chromium:848428 
TEST=Passes on soraka, caroline.

Change-Id: Icecba7b237dd7de99c4b1b590060e7e2752719af
Reviewed-on: https://chromium-review.googlesource.com/c/1259564
Tested-by: Jorge Lucangeli Obes <jorgelo@chromium.org>
Reviewed-by: Mattias Nissler <mnissler@chromium.org>

[modify] https://crrev.com/f0ea56d4f6c8f439b047159694e890a40ce89fef/client/site_tests/security_x86Registers/security_x86Registers.py

Give it a couple of days to attempt some runs.

This is now fixed: https://stainless.corp.google.com/search?view=matrix&row=test&col=build&first_date=2018-10-01&last_date=2018-10-08&suite=%5Esecurity%24&exclude_cts=true&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=false

The only failures are related to early wake-ups from suspend.

The NextAction date has arrived: 2018-10-09