Yicong-Huang opened a new pull request, #7172:
URL: https://github.com/apache/texera/pull/7172

   ### What changes were proposed in this PR?
   
   Merge-queue builds now default to four self-hosted runner tiers; PR runs opt 
in via a `ci:self-hosted` label, and push/scheduled runs stay on GitHub-hosted 
runners.
   
   - `arc-heavy-linux`: amber, amber-integration, frontend
   - `arc-medium-linux`: platform, pyamber
   - `arc-light-linux`: small service jobs plus the precheck/aggregator control 
plane
   - `arc-bench-linux`: dedicated bench machine, so benchmark numbers stay 
comparable
   
   Precheck probes runner availability and queue congestion (optional 
`ARC_STATUS_TOKEN` secret). It falls back to `ubuntu-latest` per tier when a 
set is offline or saturated. The `ARC_AVAILABLE` repo variable is a manual kill 
switch for jobs that queue before any probe can run. Step conditions switch 
from `matrix.os == 'ubuntu-latest'` to `runner.os == 'Linux'`, making the 
matrices runner-label agnostic.
   
   Rollout: 25 INFRA-provisioned runners are already registered under these 
labels; we will add the `ci:self-hosted` label and the probe secret. Without a 
label or a merge-queue entry, behavior is unchanged.
   
   ### Any related issues, documentation, discussions?
   
   Closes #7171
   
   ### How was this PR tested?
   
   - Repeated full CI rounds on a fork running this routing against a live 
25-runner fleet: all checks green, every job landing on its intended tier.
   - Fallback verified per tier: with a scale set offline, precheck routed that 
tier back to `ubuntu-latest`.
   - Label-free PR rounds confirmed hosted behavior is unchanged.
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Claude Fable 5)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to