Repository navigation
Add temporary extension mechanism to check-nightly-success - #158
KyleFromNVIDIA wants to merge 7 commits into
Conversation
If a project goes for an extended period of time without a successful nightly run, they sometimes temporarily increase their maximum days without success. Rather than doing that, provide a temporary extension mechanism that expires on a specific day, so that the max days without success never needs to be updated, and the temporary measure stays temporary, even if the extension date is never removed. This mechanism supersedes all other checks if it passes, meaning if the current date is less than the temporary expiration, GitHub is never checked for successful workflows.
|
Oh! Instead, we could have a "temp extension start" and "temp extension end", and if there were any passing runs between those two times, then the temp extension is void unless it gets renewed with a new start date. |
This reverts commit b5ca56c.
|
Temporary extension in action: https://github.com/NVIDIA/cudf/actions/runs/39962717089/job/120445673667?pr=24804#step:3:174 |
If a project goes for an extended period of time without a successful nightly run, they sometimes temporarily increase their maximum days without success. Rather than doing that, provide a temporary extension mechanism that expires on a specific day, so that the max days without success never needs to be updated, and the temporary measure stays temporary, even if the extension date is never removed.
This mechanism supersedes all other checks if it passes, meaning if the current date is less than the temporary expiration, GitHub is never checked for successful workflows.