zhengruifeng opened a new pull request, #60045: URL: https://github.com/apache/spark/pull/60045
### What changes were proposed in this pull request? Apply the same commit-count sampling introduced for branch-4.x in #57841 to post-merge `build_main.yml` runs on `apache/spark` master. A lightweight job checks out the full history and starts the existing reusable build only when `git rev-list --count HEAD` is divisible by ten. It records the decision in the job summary. The sampling check runs only on upstream master. Fork PR branches continue to build on every push, fork master syncs remain skipped, and other upstream branches retain their existing behavior. This samples the existing affected-module build; it does not turn the selected run into a full-suite build or accumulate the diffs from skipped pushes. Changes omitted by sampling may therefore wait for scheduled coverage to be exercised. Scheduled workflows are unchanged. ### Why are the changes needed? Reduce Spark's GitHub Actions consumption under the ASF resource limits by extending the existing branch-4.x sampling policy to master. For ordinary single-commit pushes, this skips nine out of ten expensive post-merge builds while retaining pre-merge CI and scheduled compatibility builds. ### Does this PR introduce _any_ user-facing change? No. This changes CI frequency only. ### How was this patch tested? - `actionlint` v1.7.11 passed for `.github/workflows/build_main.yml`. - Executed the actual sampling shell step with controlled commit counts from 1 through 30; only 10, 20, and 30 selected the build. A simulated Git failure failed the check without selecting the build. - Checked job conditions for sampled/unsampled master pushes, a failed sampling job, fork PR branches, fork master syncs, other upstream branches, and cancellation. Confirmed that skipped sampling checks do not suppress fork PR builds. - `git diff --check` passed. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Codex (GPT-6) -- 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]
