Warning: Last successful nightly checks run was more than 96 hours ago
This was intended to make us aware if we were missing emails from the nightly jobs, but it's firing more often than is probably useful when we're stuck with a failing config (since the nightly emails already tell us that). Anyone have suggestions for what its conditions to fire should be?
Would it be possible to have it fire in the event that there was neither a
successful run nor a GA Tests mail sent for 48 hours?
-Brad
Oh yeah, checking the status of the mailing job specifically rather than the whole nightly workflow run would make a lot of sense. That should be pretty simple, will try it.
Tailor nightly heartbeat warning to more relevant conditions by arifthpe · Pull Request #29412 · chapel-lang/chapel · GitHub will cause the warning to only fire if neither the nightly checks as a whole nor the send-failure-mail job have succeeded in the last 48 hours.