Some paladins report lots of "Infra failure", especially wolf-tot-paladin:
https://luci-milo.appspot.com/buildbot/chromeos/wolf-tot-paladin/?limit=200

At a glance, it looks like it's a very flaky builder and that it has recently become so. Especially if you compare it with https://luci-milo.appspot.com/buildbot/chromeos/samus-paladin/?limit=200, or https://luci-milo.appspot.com/buildbot/chromeos/cyan-paladin/?limit=200

I think what actually happens is that it's often running longer than the CQ because as far as I understand it the CQ doesn't wait for it to complete.
So it gets stopped by the Cleanup stage of the next CQ run pretty often, but it always gets reported as "infra failure" and it's not obvious at all that it was actually cleanly stopped: you have to know about the Cleanup stage of the next CQ, check the logs, find the buildbucket ID and verify that it's identical.

It would be good if paladins that are explicitly stopped by the CQ were marked as such, if possible also with a different colour code. (Note that it would also help differentiate it for more important paladins, not just wolf-tot-paladin)