On Tue, Feb 20, 2024 at 1:59 AM Edouard Choinière <e....@outlook.com> wrote: > > I don’t know a lot about backporting,
If "lucky", then it is just git cherry-pick <hash> > 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 fact the slowest CI run determines how much time I have to wait with each release step (i.e., editing VERSION file, wait 1:30hs, do some steps, wait 1:30hs, create tarball, wait 1:30hs, reset VERSION file, wait 1:30hs ... which is a pain). > 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. Okay. > Windows workflows I don’t think it’s advantageous, as more than 20 mins is > spent before starting tests. Alright. Perhaps I have simply go through it again and hope that we abandon 8.3 soon :-) Best Markus _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
