Add additional CI targets

[jmid]

We are starting to have a wonderful torture test suite.
It is however only run on Github Actions machines: Intel Linux and Intel Mac in native code mode...

Other torture targets could include:

• bytecode
• 32-bit (bytecode only for now)
• framepointer
• ARM64 architectures
• *BSD (FreeBSD, OpenBSD, ...)
• Windows (MingW, Cygwin, MSVC)

Apparently one can hook into GitHub Actions to provide our run test runner machines as "self-hosted runs" (potentially relevant for ARM64, *BSD, ...))

[n-osborne]

Would it be an idea to consider ocaml-ci?

[jmid]

Yes, I think it is (if not now then later).

The ocaml-ci that runs on https://github.com/ocaml/opam-repository runs only one flavor of 5.0 on Linux (on Intel/amd64 I suppose). I don't know if that is also the case if you enable it on project repos? 🤔 Depending on the answer, ocaml-ci may not necessarily be the solution (yet).

[jmid]

An update:

• CI: Add tests using the bytecode target #139 adds a byte code target.
• We are also investigating how to add an ARM64 runner.

[jmid]

Another update:

• Add CI workflows on Windows #179 adds a Windows target

[jmid]

A third update:

• Add the debug runtime in dune config and CI #255 adds a debug runtime target

[jmid]

Another update:

• CI 32-bit and OPAM #298 added a 32-bit target
• Add workflows to test OCaml trunk on Cygwin #305 added a Cygwin target

[jmid]

Another update: Thanks to @benmandrew we now have both Linux and macOS arm64 runners via https://github.com/ocurrent/multicoretests-ci 🎉

[jmid]

Another update:

• Add frame pointer workflows #391 added frame-pointers as a target
• Test on FreeBSD ocurrent/multicoretests-ci#26 added FreeBSD testing via https://github.com/ocurrent/multicoretests-ci