Viktor Szakats

It seems one of those OpenBSD-specific extra security warnings. Could explain why it doesn't trip on `-Werror`. If the code looks okay, it's safe to ignore. _If_ it has an...

Running tests in these env is risky, and it's done at this point for FreeBSDs and OmniOS. The latter had this fallout: ``` TESTFAIL: These test cases failed: 1119 1167...

> Both are static test scripts. Both depending on a C preprocessor `cpp`. Likely this is where it fail on this OS.

This method supports other BSDs and OmniOS, along with arm64 support. Also multiple versions of these OSes. The configuration is more familiar, being GHA. ~~Also since it's GHA, it's possible...

All clear (with `!1119 !1167` for OmniOS), except OpenBSD, where these fail (out of 2 runs): ``` TESTFAIL: These test cases failed: 271 283 284 285 286 332 1007 1009...

OpenBSD 1167 failure is this: ``` test 1167...[Verify curl prefix of public symbols in header files] perl -I/home/runner/work/curl/curl/tests returned 1, when expecting 0 1167: exit FAILED == Contents of files...

Without building examples: https://github.com/curl/curl/actions/runs/9086774834/job/24973212987 With building examples: https://github.com/curl/curl/actions/runs/9087097071/job/24974151469 ``` build examples no yes ------- ------- NetBSD: 13m 1s 13m 5s OpenBSD: 4m 50s 5m 28s FreeBSD autotools: 12m 44s 13m...

These new tests are ready to merge. They also might need tweaking if they turn out to be unstable or too much load. The autotools job for FreeBSD is slow,...

I plan to merge this today. If the new jobs turn out to be more pain than gain, I'm perfectly fine with tuning and/or deleting any/all of them. If it...

Post-merge update: Right after merging, one PR failed in OmniOS running MQTT tests, and an FTP test in another job. This hasn't happened throughout the almost 100 runs while working...