From 45f8b1ca9e5dd1e28c08f7492e7cb9f172334bd1 Mon Sep 17 00:00:00 2001 From: Chris Evich Date: Tue, 6 Dec 2022 10:38:10 -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 3a3d465828..13be3f9910 100644 --- a/.github/workflows/check_cirrus_cron.yml +++ b/.github/workflows/check_cirrus_cron.yml @@ -11,7 +11,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/6707778565701632 - - cron: '59 23 * * 1-5' + - cron: '03 03 * * 1-5' # Debug: Allow triggering job manually in github-actions WebUI workflow_dispatch: {} # Allow re-use of this workflow by other repositories diff --git a/.github/workflows/rerun_cirrus_cron.yml b/.github/workflows/rerun_cirrus_cron.yml index 8ac3330319..e72b78b81a 100644 --- a/.github/workflows/rerun_cirrus_cron.yml +++ b/.github/workflows/rerun_cirrus_cron.yml @@ -10,7 +10,7 @@ on: schedule: # N/B: This should fire about an hour prior to check_cirrus_cron # so the re-runs have a chance to complete. - - cron: '05 22 * * 1-5' + - cron: '01 01 * * 1-5' # Debug: Allow triggering job manually in github-actions WebUI workflow_dispatch: {} # Allow re-use of this workflow by other repositories