I added a workflow to check if the fuzzer build still works. It will build the fuzzers like described in docs/FUZZING.md and after the build succeeds, it will run each fuzzer for a short time to check if there is an obvious runtime error.
To give an example, there are two commits on this branch. 0f9bfee0 will fail at compile time. c1792afb will be caught by ASAN when running the fuzzers.
You should be able to see the workflow runs for the example commits here.
Right now, it only runs on Linux. Should we also test this on Windows or Mac?
I added a workflow to check if the fuzzer build still works. It will build the fuzzers like described in
docs/FUZZING.mdand after the build succeeds, it will run each fuzzer for a short time to check if there is an obvious runtime error.To give an example, there are two commits on this branch. 0f9bfee0 will fail at compile time. c1792afb will be caught by ASAN when running the fuzzers. You should be able to see the workflow runs for the example commits here.
Right now, it only runs on Linux. Should we also test this on Windows or Mac?
fix #926