Calvin, I did try splitting them into chunks to be able to run them parallel when I migrated CI from Concourse (earlier CI infrastructure) to GithubActions last year. Geode has unit, integration, acceptance and distributed tests which are different forms of tests. As of today, the pipeline runs unit, integration and acceptance tests successfully. But distributed tests are too compute heavy (as each test runs a cluster), which I tried splitting them by submodule which aren't enough, some modules can run these tests and some cannot (going to package level could be an option to further slice them). GHA has a max timeout of 6hours so anything that is possible to run with in 6hrs is good.
https://github.com/apache/geode/actions/runs/6287813917 Rich, I will try to reach out to build-infra and see what can be done to address this CI issue. Sai On Tue, 12 Nov 2024 at 06:37, Rich Bowen <rbo...@rcbowen.com> wrote: > > > > 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 > > > > >
