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.
Best regards
Tim Düsterhus
