Failures in Rollback FAFT tests corrupting images

[Marc Jones]

I am testing Rambi and another Baytrail device with the tot FAFT test. I am seeing failures in Rollback Kernel in multiple attempts. I think that the dut and USB device are getting out of sync and not restoring the kernel correctly. Are there any know issues with the current tot FAFT in this area? Is there a know good commit that I should build for testing Rambi? 

Thanks,

Marc

[Danny Chan]

Which test you are running ? What version of chromeOS?

You might need to reflash the USB with a new iamge and rerun the test.

To unsubscribe from this group and stop receiving emails from it, send an email to faft-users+...@chromium.org.

[Marc Jones]

Hi Danny, 

This is running the faft_bios suite and we see frequent problems in firmware_RollbackKernel on multiple systems with multiple test runs. The test passes when it is run individually. We reimage the USB and the dut, because both may be in a bad state. We are testing with the current tot; autotest, firmware, and CrOS for Rambi. We have tried to isolate the test to interactions with a previous test, but have not been successful. Any ideas would be helpful. 

Regards,

Marc

[Danny Chan]

We have seen that here also, we are trying to figure out what. But in the mean time you can try to run faft_lv1 to faft_lv5, they group related bios tests.

[Marc Jones]

Hi Danny, 

OK, Thanks for the update. I will continue to debug as best I can. It is hard to capture the state when it fails. I'll let you know if I find any details.

Marc