I don’t know a lot about backporting, but if you’re talking about splitting of the Ubuntu workflow’s gunittest tests, I don’t see a reason why the content of the changes couldn’t be copied to a new commit for that branch too. Since they are ran less often, the tests could be split in three or even 4 jobs, where the %of time spent compiling the same code would be a bit higher, but the time for all tests to run could be smaller. The tests in the temporal folder still take half the total test time though.
If you are talking about the macOS arm runner, it might require some other changes to port. My opinion would be to leave that alone in the 8.3 as pre-arm code. But the same splitting could easily be done for 8.3, and split as wished. In main, for macOS workflows, with only 20-25 mins spent on tests, with 3-4 min spent on compiling, I don’t see the need to split it. Windows workflows I don’t think it’s advantageous, as more than 20 mins is spent before starting tests. Edouard Choinière > Le 19 févr. 2024 à 19:00, Markus Neteler <[email protected]> a écrit : > > Hi Edouard, > > Do you see a chance to backport the CI speed updates to G83? That would make > my release manager life much easier as the ever lasting waiting would > probably halfen ... :) > > I could also cherry-pick that in case. > > Best > Markus _______________________________________________ grass-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/grass-dev
