Sometimes the failure summary that appears in the output of a failed PFQ HWTest does not appear in the autofiled bug.

Example:
https://uberchromegw.corp.google.com/i/chromeos/builders/tricky-chrome-pfq/builds/2013

The first failure summary shows:

[Auto-Bug]: hardware_RamFio: 23 reports, FAIL: Autotest client terminated unexpectedly: DUT rebooted during the test run.
[Test-Logs]: hardware_RamFio: FAIL: Autotest client terminated unexpectedly: DUT rebooted during the test run.

However the comment corresponding to that failure shows:

[bvt-cq] hardware_RamFio Failure on tricky-chrome-pfq/R53-8480.0.0-rc2

This report is automatically generated to track the following Failure:
Test: hardware_RamFio.
Suite: bvt-cq.
Chrome Version: None.
Build: tricky-chrome-pfq/R53-8480.0.0-rc2.

Reason:
None.

[log links]

ANCHOR  TestFailure{bvt-cq,hardware_RamFio,None}


ALSO: The autofiled bugs do not link back directly to the build where they failed. This can be useful to provide additional context for the failure.