> On Nov 12, 2024, at 2:05 AM, Calvin Kirs <k...@apache.org> wrote: > > Hi Sai, > On Tue, Nov 12, 2024 at 2:28 PM Sai Boorlagadda <sai.boorlaga...@gmail.com > <mailto:sai.boorlaga...@gmail.com>> > wrote: > >> Thanks Sanjay for your contribution. The challenges on testing aren't >> broken builds (as far I remember develop should be stable and should have >> all tests pass), rather the challenges are that the Distributed Tests are >> taking longer than the max timeout allowed (6hrs) on github actions. So as >> far as I remember there aren't any failing tests other than that we don't >> have ability to run them successfully as the tests demand higher >> configuration virtual machines to complete them in a meaningful time. >> > > If we're limited to using only the default GitHub Action runners and our > test code is fully optimized, we could consider splitting our tests into > groups (such as by package name prefix) and creating multiple workflows to > run them in parallel. This way, we can distribute the testing load and > potentially speed up the overall CI process.
I encourage all of you to subscribe to bui...@apache.org <mailto:bui...@apache.org> and/or go to the #builds slack channel on the-asf.slack.com and ask there. There are other options than GitHub Actions, and Infra has specific recommendations for cases like yours. Please don’t be limited by how you’ve done things in the past. — Rich Bowen rbo...@rcbowen.com
