hello-stephen opened a new pull request, #66958:
URL: https://github.com/apache/doris/pull/66958

   ## Background
   
   `BE UT (macOS)` is the largest consumer of the GitHub Actions queue: in a 
recent 48h sample it used 1112h of runner wall-clock (44% of all workflows, ~23 
concurrent slots against the 5-slot macOS concurrency limit) and spent 355h 
queued, with a max queue wait of 41.7h. 496 runs were created (486 from PRs), 
of which 228 did no work (paths filter mismatch) and ~195 did a full BE build.
   
   This workflow only verifies that the BE compiles on macOS — it does not run 
unit tests (see the comment in the workflow). Running it on every PR push is 
far beyond what the macOS pool can absorb.
   
   ## Changes
   
   1. **Trigger change**: run on `push` to `master` (~18 merges/day) instead of 
every `pull_request` synchronize (~100 builds/day).
   2. **Schedule reduced**: `0 4,10,16,22 * * *` → `0 4 * * *` (one daily cache 
warm-up instead of four).
   3. **Paths filter removed**: with only `push`/`schedule` triggers left, the 
job-level paths filter has nothing to filter and is deleted; the build step now 
always runs.
   4. **`timeout-minutes: 360` added**: some runs were observed to hang for up 
to 24h.
   
   ## Behavior change
   
   PRs no longer get a macOS compile check during development; failures surface 
on the master branch after merge. This trades PR-level macOS coverage for queue 
relief. If PR-level coverage is wanted again later, it can be re-added 
selectively (e.g. label-triggered or sampled) within the ~5-slot macOS capacity.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to