Skip to content
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

Silly change #13

Closed
wants to merge 36 commits into from
Closed

Silly change #13

wants to merge 36 commits into from

Conversation

dra27
Copy link
Owner

@dra27 dra27 commented Mar 10, 2022

No description provided.

dra27 added 30 commits March 9, 2022 12:24
Use the src_ext/archives cache in all jobs which build opam. The
archives-cache stage is converted to a general analysis phase,
determining cache keys to use throughout the workflow from a single
checkout at the start.
Zarith contains an unecessary dependency on ocamldoc in its configure
script - instead of installing ocamlbuild, a fake error-triggering
script is installed in ocamldoc's place.
Passing the version explicitly to the creation script is clearer, and
also eliminates a duplicate (in several cases, the default for
OCAML_VERSION could be out-of-sync with a strategy matrix, breaking
caching).
Don't use OS in matrices - stops macOS from holding up the feedback
obtained from testing.
Since the latter displays an error message
It takes so long, it's better to do it alongside the main job for
parallelism.

Merging into the build matrix would improve this further.
The GitHub Actions runners use a Windows short path name for %TEMP%
which fouls up the reftests - normalising with Unix.realpath will fix
the problem, at least for OCaml 4.13+
Temporary commit - this should be handled by msvs-detect
dra27 and others added 4 commits March 9, 2022 12:27
@dra27 dra27 force-pushed the all-your-base-test-pr branch 4 times, most recently from 1ddbec1 to ead2d38 Compare March 10, 2022 11:40
The idea here is that a PR which breaks opam fails at build rather than
failing at the caching stage.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants