From 3212bbed6fd512daec158cf5d231ae63ec9ab279 Mon Sep 17 00:00:00 2001 From: Chris Evich Date: Tue, 6 Dec 2022 10:18:45 -0500 Subject: [PATCH] [skip-ci] GHA/Cirrus-cron: Fix execution order Fairly universally, the last Cirrus-Cron job is set to fire off at 22:22 UTC. However, the re-run of failed jobs GHA workflow was scheduled for 22:05, meaning it will never re-run the last cirrus-cron job should it fail. Re-arrange the execution order so as to give plenty of time between the last cirrus-cron job starting, the auto-re-run attempt, and the final failure-check e-mail. Signed-off-by: Chris Evich --- .github/workflows/check_cirrus_cron.yml | 2 +- .github/workflows/rerun_cirrus_cron.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/check_cirrus_cron.yml b/.github/workflows/check_cirrus_cron.yml index 33ef3ac2..7dcd3f39 100644 --- a/.github/workflows/check_cirrus_cron.yml +++ b/.github/workflows/check_cirrus_cron.yml @@ -9,7 +9,7 @@ on: # N/B: This should correspond to a period slightly after # the last job finishes running. See job defs. at: # https://cirrus-ci.com/settings/repository/6706677464432640 - - cron: '59 23 * * 1-5' + - cron: '03 03 * * 1-5' # Debug: Allow triggering job manually in github-actions WebUI workflow_dispatch: {} diff --git a/.github/workflows/rerun_cirrus_cron.yml b/.github/workflows/rerun_cirrus_cron.yml index 4746b191..d3ee64cc 100644 --- a/.github/workflows/rerun_cirrus_cron.yml +++ b/.github/workflows/rerun_cirrus_cron.yml @@ -8,7 +8,7 @@ on: # N/B: This should correspond to a period slightly after # the last job finishes running. See job defs. at: # https://cirrus-ci.com/settings/repository/6706677464432640 - - cron: '05 22 * * 1-5' + - cron: '01 01 * * 1-5' # Debug: Allow triggering job manually in github-actions WebUI workflow_dispatch: {}