In case anyone's puzzled by that four-days-later message blaming one
push for a regression that was previously blamed on two pushes, if you
just load up self-serve for the push which didn't get a run of that
talos job, find where it's listed in the Builds section despite not
having actually run on that push, and rebuild it, then it will be run on
that push.
The regression itself looks like just noise to me, but we are not stuck
with the effects of coalescing, we can retrigger around them, even
though,
https://bugzilla.mozilla.org/show_bug.cgi?id=787447#c10, I think
the regression script should be the one to do the retriggering before it
sends anything, not us after it sends something bogus.