Max has a PR https://github.com/apache/iceberg/pull/13675 which speeds up the tests by running them parallel. While any parallelism introduces potential flakiness, it could halve the CI speed which would be also nice along the changes here.
Fokko Driesprong <fo...@apache.org> ezt írta (időpont: 2025. aug. 25., H, 9:22): > TIL about the merge queue, but I'm all aboard. I think this would be great > to have, especially on the Iceberg Java side where the CI takes some time > to run. > > Kind regards, > Fokko > > Op ma 25 aug 2025 om 08:43 schreef Eduard Tudenhöfner < > etudenhoef...@apache.org>: > >> I like the idea of having a merge queue, so +1 to that. >> >> On Mon, Aug 25, 2025 at 7:47 AM Jean-Baptiste Onofré <j...@nanthrax.net> >> wrote: >> >>> Hi >>> >>> Thanks for the idea! >>> I like to require branches to be up to date before merging: the merge >>> queue provides basically similar protection, but more "flexible" when >>> a lot of PRs are merged every day. >>> >>> I checked from ASF standpoint, and the merge queue can be enabled >>> without issue (at infra level). I don't think we need anything in the >>> .asf.yaml, but if needed we have to create a ticket to infra (if >>> needed and after consensus here). >>> >>> Regards >>> JB >>> >>> On Mon, Aug 25, 2025 at 3:54 AM Renjie Liu <liurenjie2...@gmail.com> >>> wrote: >>> > >>> > Hi, all: >>> > >>> > I want to raise a discussion about enabling merge queue in iceberg >>> related repositories. >>> > >>> > In short, github merge queue improves efficiency of maintainers for >>> repo with high velocity. When there are several prs ready for merging, >>> instead of asking the author/maintainer to merge with the main branch >>> manually before merging, it will put ready to merge prs to a queue, update >>> them to the latest commit, and run all required checks one by one. When all >>> checks passed, it will do the merge automatically. >>> > >>> > Looking forward to hearing your thoughts! >>> >>
