Closed stweil closed 1 year ago
Elegant!!
I looked at the example, and saw it did 147 tests. I've been getting 146 when run locally using alltests_reg. Comparing the set, I found that numa3_reg.c had been omitted from alltests_reg, for no good reason. So I'll add it.
@DanBloomberg, I wonder whether the new action really should be triggered by every pull request and git push. In addition it can be triggered manually by project maintainers (url). Each action run uses two CPU cores for 12 minutes, one for macOS 12 and one for macOS 13.
Maybe it would be sufficient to run only on macOS 13 by default, so macOS 12 would only be tested when that was requested manually. What do you think?
Running by default only with macOS 13 is fine with me.
Considering possible overuse of github resources, what do you think about the fuzzing that is run on every git push? (I don't know if it is run with PRs)
The fuzzing action is only triggered by pull requests, see the code. It typically runs for about 30 minutes (see history). That looks like a waste of resources, for example electrical energy, because Google's OSS-Fuzz also runs fuzzers for Leptonica (not only for a few minutes which won't find issues, but really long) and reports build errors by e-mail. @AdamKorcz, what do you think?
See this example for the new action.