Skip to content

docs(ci,#15941): aligner runner-starvation-advisory sur sa matrice reelle (2 labels) #15947

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jsboige wants to merge 1 commit into from
Closed

docs(ci,#15941): aligner runner-starvation-advisory sur sa matrice reelle (2 labels) #15947

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions .github/workflows/runner-starvation-advisory.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
name: Runner starvation advisory (waiter+linux+lean)
name: Runner starvation advisory (waiter+lean)

# Sonde d'extinction multi-labels (issue #14846, grain c.1063 myia-po-2027).
# Le 2026-09-05 entre 20:26Z et 00:52Z, le pool `coursia-waiter` est tombe
Expand All @@ -8,12 +8,13 @@ name: Runner starvation advisory (waiter+linux+lean)
# L'organe `scripts/ci/check_runner_starvation.py` mesurait deja le predicat
# EXTINCTION (zero runner online sur le label), mais le seul workflow qui
# l'appelait (`linux-runner-starvation-advisory.yml`) ne couvrait que
# `coursia-linux`. Cette sonde etend la couverture aux 3 labels requis par
# `pr-gate.yml` (waiter) + workflows bloquants (linux, lean).
# `coursia-linux`. Cette sonde etend la couverture a 2 des 3 labels requis
# (`pr-gate.yml` waiter + workflows bloquants lean) ; le troisieme,
# `coursia-linux`, reste couvert par `linux-runner-starvation-advisory.yml`.
#
# Pourquoi une matrice et pas 3 workflows dedies : un seul cron centralise
# l'observabilite, les 3 sondes partagent la fenetre STARVATION et le secret
# RUNNERS_READ_PAT, et la matrice GitHub Actions parallellise les 3 mesures
# Pourquoi une matrice et pas 2 workflows dedies : un seul cron centralise
# l'observabilite, les 2 sondes partagent la fenetre STARVATION et le secret
# RUNNERS_READ_PAT, et la matrice GitHub Actions parallellise les 2 mesures
# sans collision de rate-limit. Schedule dediee (cron offset 19,49 pour
# coursia-linux + 23,53 pour les 2 autres -- l'offset disjoint evite de
# charger le meme runner sur 2 vagues consecutives).
Expand All @@ -23,7 +24,7 @@ name: Runner starvation advisory (waiter+linux+lean)
# - predicat STARVATION : si jobs queued > seuil SANS aucun in_progress ->
# ::error:: (symptome distinct de l'extinction -- file profonde qui ne
# draine pas)
# - WARN floor configurable par label (waiter = 1, linux = 2, lean = 1)
# - WARN floor configurable par label (waiter = 1, lean = 1)
#
# Acceptance A2 (persistance systemd) deja livree par PR #14981 (waiter) +
# PR #15401 (lean). Acceptance A3 (verification systemctl is-enabled po-2024)
Expand Down Expand Up @@ -53,7 +54,6 @@ jobs:
# le label qu'il observe mourrait avec lui. Meme raisonnement que
# linux-runner-starvation-advisory.yml l.44-46.
runs-on: [self-hosted, coursia-ephemeral, coursia-linux]
if: github.event.pull_request.head.repo.full_name == null || github.event.pull_request.head.repo.full_name == github.repository
timeout-minutes: 10
strategy:
fail-fast: false
Expand Down
Loading