Hello here, I did not want to nudge anyone here, but since Andrew does it. Just adding Andrew - who keeps on nudging Airflow in issues - we are working in Airflow on implementing **way** more improvements than that - for several weeks already - and we are close to conclusion. And the only way to deal with queueing is to get big users (Airflow and Arrow) are two biggest users of the CI in ASF. In Airflow we are working on 80% cutting - via using self-hosted runners and via delegating CI to the contributor's public runners.
And we are explaining that for weeks, yet, for some reason we get nudges from Andrew every day - even if he knows very well we are working on it. And - just to be sure - those 30% - 40% savings above are easily achievable (way easier than the 80% of Airflow) - and it is also absolutely necessary to remove the pressure from the queue., Andrew, Andrew, are you actually working with other Arrow team members on applying those improvements I proposed (or other?). It seems a bit one sided when you have all proactiveness from our side, yet we do not hear what you are doing to help the ASF. I would really appreciate **some** answer here how are you working with others in the Arrow to solve the issues. Are there any plans to improve things ? And yes Andrew - I expect answer from you, J. On Thu, Oct 22, 2026 at 8:46 PM Benson Muite <[email protected]> wrote: > Jarek Potiuk <[email protected]> writes: > > Hi, > > > Hi everyone, > > > > I hope you're all doing well! I've been looking at how Arrow uses > > GitHub Actions. All ASF projects share the same pool of GitHub > > runners, so every minute we save also shortens the queue for > > everyone else. The good news: Arrow's CI is already in good shape > > (path filters, concurrency cancelling, the "CI: Extra" labels, > > RunsOn for CUDA). Even so, I found some easy wins, and I'd love to > > hear what you think. > > > > I was a listener at yesterday's board meeting and i understand > > that Arrow has some CI "difficulties" and is looking for ways to > > deal with and JBO was generally offering his overlook of that > > (hence the CC:) but then there was a lot of buzz about the > > #project-workflows-optimisations channel of ASF - and I just added > > new "workflow-optimization" skill in Magpie that is > > producing very good advice, and you can use it to implement changes. > > those optimizations quickly. > > > > Last week we used roughly 110-125k GitHub-hosted runner minutes. > > Package Linux alone is about 40% of that. > > Fedora does offer CI builds for packaging: > https://packit.dev/ > > Probably CentOS and other RPM builds could be moved to that. >
