On Wed, Mar 16, 2022 at 09:31:56AM +0100, Tim Düsterhus wrote: > Willy, > > On 3/8/22 20:43, Tim Düsterhus wrote: > >> Yes my point was about VTest. However you made me think about a very good > >> reason for caching haproxy builds as well :-) Very commonly, some VTest > >> randomly fails. Timing etc are involved. And at the moment, it's impossible > >> to restart the tests without rebuilding everything. And it happens to me to > >> click "restart all jobs" sometimes up to 2-3 times in a row in order to end > > > > I've looked up that roadmap entry I was thinking about: A "restart this > > job" button apparently is planned for Q1 2022. > > > > see https://github.com/github/roadmap/issues/271 "any individual job" > > > > Caching the HAProxy binary really is something I strongly advice against > > based on my experience with GitHub Actions and CI in general. > > > > I think the restart of the individual job sufficiently solves the issue > > of flaky builds (until they are fixed properly). > > > > In one of my repositories I noticed that this button is now there. One > can now re-run individual jobs and also all failed jobs. See screenshots > attached. >
Hello Tim, It looks like it is available as well on our repositories, I just test it and it works correctly. Honestly I really don't like the dependency to another repository with a format specific to github. I agree that a cleaner integration with github with their specific tools is nice, but I don't want us to be locked with github, we are still using cirrus, travis, sometimes gitlab, and also running some of the scripts by hand. We also try to avoid the dependencies to other projects and its much simplier to have few shell scripts and a CI configuration in the repository. And typescript is not a language we would want to depend on if we need to debug it for example. Giving that github is offering the job restart feature, we could skip the VTest caching, since it's a little bit ugly. Only the quictls cache need to be fixed. Regards, -- William Lallemand
