portable/.github/workflows/cifuzz.yml, branch v4.3.0

ci: improve cifuzz workflow

2026-04-12T17:33:51+00:00

ci: update and pin github actions

2025-12-18T12:43:25+00:00

What happens on ubuntu-24.04?

2025-01-09T13:36:26+00:00

Actions have been issuing annoying warnings about ubuntu-24.04 becoming the default for ubuntu-latest for some definition of "soon". Let's see if we care.

ci: update actions

2024-08-25T18:04:39+00:00

ci: add event number to concurrency group

2024-05-29T07:25:18+00:00

ci: add concurrency groups to workflows

2023-12-19T14:33:08+00:00

there has to be some trigger, even a manual one

2023-11-28T13:06:03+00:00

disable periodic builds of broken CI workflows

2023-11-28T06:30:22+00:00

Neither of these has built in over a month. Solaris looks to be an upstream timeout issue (seems the hack it uses may not work anymore). Not sure if cifuzz is really needed either, since we're still being tested through clusterfuzz actively.

change the trigger for running fuzzer tests

2023-07-07T05:34:16+00:00

Since fuzzers benefit more from being run regularly on the openbsd tree, and they take a long time, does it make more sense that the trigger is a cron like the Coverity job? They sometimes don't work in branches anyway, since the fuzz builds rely on external code being updated to match the master branch.

CI: add CIFuzz action

2022-11-19T12:31:40+00:00

Signed-off-by: David Korczynski