zhengruifeng commented on PR #60045: URL: https://github.com/apache/spark/pull/60045#issuecomment-6599073806
Updated the proposal to **run master post-merge CI once every five commits (20%)**, rather than once every ten. This doubles the retained build frequency while keeping the proportional usage estimate below both ASF runner-minute limits in the measured period. Using the calendar week October 26-November 1, 2026 and the rolling five-day analysis in the usage comment: | Master build frequency | Estimated weekly minutes | Weekly headroom | Estimated peak five-day minutes | | --- | ---: | ---: | ---: | | 1 in 3 | 255,124 | 5,124 over limit | 196,607 | | 1 in 4 | 247,240 | 2,760 | 190,898 | | **1 in 5 (proposed)** | 242,509 | 7,491 | 187,480 | | 1 in 10 | 233,048 | 16,952 | 180,643 | | **ASF limit** | **250,000** | | **216,000** | One in three would still exceed the weekly budget by about **5,124 minutes**. One in four would leave only **2,760 minutes** of weekly headroom. Starting with one in five leaves about **7,491 minutes weekly** and **28,520 minutes over five days**, so it is a more practical starting point with more coverage than one in ten. These are proportional projections from reconstructed hosted-job runtime, assuming comparable sampled run costs and ordinary single-commit pushes. They exclude the added lightweight gate cost; actual usage should be monitored after rollout. The separate ASF limit of 20 concurrent jobs per workflow still needs a concurrency fix: changing sampling frequency does not cap the retained runs. -- 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]
