-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: Add native and bytecode workflows using MSVC #399
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks again for this 🙏 MSVC has been merged so we should get this nice PR rolling! 😃
A little fiddling is required I believe:
- This should target
ocaml/ocaml
trunk rather thandra27/ocaml
IIUC - The workflows should be renamed to
msvc-530-trunk.yml
andmsvc-530-trunk-bytecode.yml
to fit into the existing naming scheme
A few questions:
- Is the source code install of
dune
andqcheck
still required, or can we go with opam now? - I suppose this is not set up to easily test PRs and feature branches? (just asking, Cygwin + multicoretests-ci doesn't support this ATM either)
Avoid running QCheck tests as part of a `dune runtest` even if it is vendored
Add a native workflow and a bytecode one using MSVC Run the bytecode-only in two parts, like Cygwin Use the current bleeding edge versions of dune and QCheck as they recently merged fixes that are relevant for these workflows Add badges for those two new workflows
CI summary for 9ce6e3e:
(Note: CI on this PR is still targeting Out of 37 workflows 6 failed all with genuine issues |
CI summary for merge to
Out of 38 workflows 5 failed all with genuine issues |
Add a native workflow and a bytecode one using MSVC
Run the bytecode-only in two parts, like Cygwin, since preliminary results seem to suggest the test suite will require more than 6 hours to complete
Use the current bleeding edge versions of dune and QCheck as they recently merged fixes that are relevant for these workflows
Add badges for those two new workflows, on a separate line, as they aren’t really on
trunk