Currently, when a FirmwareTest which calls the check_state method fails, it fails with a message that isn't so helpful.
For example,
TestFail: Not succeed: calling <bound method FAFTCheckers.crossystem_checker of <autotest_lib.server.cros.faft.utils.faft_checkers.FAFTCheckers object at 0x7f09869fb3d0>> with args ({'recovery_reason': '193', 'mainfw_type': 'recovery'},) returning False
It doesn't report back what actually failed. You can find this information in the logs, but I think it would be better if it were reported here. This is the string that's bubbled up to to the dashboards and such.
Here's what is shown in the full debug logs:
06/08 04:44:45.194 INFO | faft_checkers:0105| Expected 'recovery_reason' value '193' but got '0'
06/08 04:44:45.195 INFO | faft_checkers:0105| Expected 'mainfw_type' value 'recovery' but got 'normal'
Comment 1 by sheriffbot@chromium.org
, Jun 12 2017Status: Untriaged (was: Available)