To reduce wasting time for CQ runs that are doomed to fail, the CQ self-destructs when any of the important paladins fail.

It would be more efficient for the sherifs/devs/infra folks to hone in on the failing paladin if the ChromeOS Commit Bot output was sorted such that the failing paladins were listed first.

For example, consider the following self-destructed run:
https://chrome-internal-review.googlesource.com/c/chromeos/ap-daemons/+/545645#message-07d2ae1644ee57092135b8d8352d521ee937fc20

The paladin that caused the failure was gale-paladin. One has to scroll over many self-destructed paladins before noticing that gale-paladin was the culprit.

Feature request is to have the paladin that caused the actual failure (gale-paladin in this particular instance) to be listed first in the bot output.