From 0619892cab8a5cc24e25f7eddcff7316757a1ff0 Mon Sep 17 00:00:00 2001 From: Aiden Grossman Date: Tue, 18 Mar 2025 19:32:39 +0000 Subject: [PATCH] [CI] Bump max workflow to process count in metrics This patch bumps the maximum number of metrics to look through when collecting metrics data. We are currently running into issues where we are losing data due to the most recent 1000 workflows not containing the workflows that we actually need to query. Just double it for now. I plan on monitoring this reasonably closely to ensure we do not run into issues, mainly API rate limits. --- .ci/metrics/metrics.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.ci/metrics/metrics.py b/.ci/metrics/metrics.py index 1463ab43a812..511b1866ed48 100644 --- a/.ci/metrics/metrics.py +++ b/.ci/metrics/metrics.py @@ -43,7 +43,7 @@ GITHUB_JOB_TO_TRACK = { # This means we essentially have a list of workflows sorted by creation date, # and that's all we can deduce from it. So for each iteration, we'll blindly # process the last N workflows. -GITHUB_WORKFLOWS_MAX_PROCESS_COUNT = 1000 +GITHUB_WORKFLOWS_MAX_PROCESS_COUNT = 2000 # Second reason for the cut: reaching a workflow older than X. # This means we will miss long-tails (exceptional jobs running for more than # X hours), but that's also the case with the count cutoff above.