OK, it wasn't quite 'next week', but :P
I figured out why this was broken, finally. The 'special' configuration
for the two-week Atomic reports (mail them to a different set of
addresses, and only mail on failure) relied on the fedfind 'milestone'
for these composes being 'Atomic', but I changed that back in
https://pagure.io/fedora-qa/fedfind/c/8c979e22cba0138b0bdc8414c86048a4a17...
and
https://pagure.io/fedora-qa/fedfind/c/26c556019bd9c4e4b9fd8cc05164bf18630...
, all for terribly good reasons of course. I've now tweaked check-
compose so you can override the configuration by the release's "dist"
(which is what Pungi/productmd refer to as the 'shortname' - it's the
first component of the compose ID, so 'Fedora', or 'Fedora-Atomic', or
'Fedora-Docker', etc.) instead of its "milestone", and tweaked the
configuration of the check-compose deployment in Fedora infra to match.
So if I got all that right, this should now work again.
I also updated the list of addresses the mails will be sent to; it was
previously Mike McGrath plus atomic@ , but I don't think Mike's the
right person any more, so I changed it to Dusty, Colin and atomic@. So
Dusty, Colin and the list should get the reports *only if* either of
the tests failed. When both tests pass, no report will be sent out.
Thanks folks!