I'm having a problem running FAFT on Swanky. It seems that FAFT has
become much less stable in the last several weeks. I don't think that
this is a DUT issue.
Initially, I couldn't get the FAFTSetup test to run, but that is fixed
by this change:
https://chromium-review.googlesource.com/#/c/202721/
Next, the full buis_suite fails on the 15th test with the following:
/tmp/faft_bios_results_swanky/results-14-firmware_CorruptFwSigA
[ FAILED ]
/tmp/faft_bios_results_swanky/results-14-firmware_CorruptFwSigA
FAIL: Unhandled
NameError: global name 'next_step' is not defined
/tmp/faft_bios_results_swanky/results-14-firmware_CorruptFwSigA/firmware_CorruptFwSigA.normal
[ FAILED ]
/tmp/faft_bios_results_swanky/results-14-firmware_CorruptFwSigA/firmware_CorruptFwSigA.normal
FAIL: Unhandled NameError: global name
'next_step' is not defined
Nothing else will pass after this failure. I am going to do some
single tests and check some more results this morning, but I wonder if
that is worth doing. I am also considering reverting back to when
rambi based FAFT was working.
Thoughts?
Marc