chore(oxcaml): CI with opam instead of nix#12763
Conversation
|
That's fine by me. The nix CI wasn't meant to get in the way, but to aid reliability. When the scope of dependencies we need to pull into the test suite settles a bit we can think a bit about adapting the nix support and enabling it again. |
Signed-off-by: Arthur Wendling <arthur@tarides.com>
86ea8f8 to
de30345
Compare
|
While you are on this, let's put this job directly in I believe the cache will be populated after this first run so best to wait for it to finish. When you push the next change we will see the cache hit too. |
shonfeder
left a comment
There was a problem hiding this comment.
FWIW, I think breaking this out of the workflow.yaml, as done here makes fine sense. But don't have a strong opinion either way, and I don't think there's any need to block on that.
Signed-off-by: Arthur Wendling <arthur@tarides.com>
Temporarily switch back to the previous CI for OxCaml to enable testing of #12707 and #12762. The Nix CI was introduced in #12632 and should be a lot more resilient in the long term. However I wasn't able to fix it to use the published OxCaml (instead of a dev version) and the new packages from the oxcaml opam-repo that
ppx_inline_testtransitively relies on.