I've been seeing more stale warnings on the status page over the last couple weeks. This seems to be caused by two issues
- Long delays in scheduled GH Action workflows as discussed in Unexpected delay in scheduled GitHub Actions workflows using cron #156282
- Failed jobs because they hit our 10min timeout.
Can't do anything about [1], but we could look into [2] to make sure that the jobs that do run can complete successfully.
Potential solutions
- Short-term: Increase timeout-minutes to 15? 20?
- Long-term: look into speeding up the job. - One thought is there are the number of workflows will keep growing and is potentially slowing down the materialized view creations. We could revisit this TODO
|
/* XXX TODO: Push created_at into the GitHub API call. The API can |
|
* handle created timesetamp¹ with operators = <> > >= < <=.² This |
|
* would avoid a bunch of pagination requests for the list call. |
|
* -trs, 18 Dec 2024 |
|
* |
|
* ¹ <https://docs.github.com/en/rest/actions/workflow-runs?apiVersion=2022-11-28#list-workflow-runs-for-a-workflow> |
|
* ² <https://docs.github.com/en/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates> |
|
*/ |
I've been seeing more stale warnings on the status page over the last couple weeks. This seems to be caused by two issues
Can't do anything about [1], but we could look into [2] to make sure that the jobs that do run can complete successfully.
Potential solutions
status/pathogen-workflows.sql
Lines 221 to 228 in 3c51133