Skip to content

Conversation

@JasonGross
Copy link
Collaborator

This shares structure a lot more, and will also enable us to (eventually) just check if the generated OCaml code is identical across Coq versions and platforms.

Note that we no longer check generated files on most platforms, and we only validate on Coq master.

@JasonGross JasonGross force-pushed the unify-ci branch 10 times, most recently from dc1b2e5 to d8c82be Compare December 26, 2023 01:12
@JasonGross
Copy link
Collaborator Author

Hm, probably it would be better to use reusable workflows rather than blocking future steps across platforms

This shares structure a lot more, and will also enable us to
(eventually) just check if the generated OCaml code is identical across
Coq versions and platforms.

Note that we no longer check generated files on most platforms, and we
only validate on Coq master.
@JasonGross JasonGross marked this pull request as draft December 26, 2023 20:05
@andres-erbsen
Copy link
Contributor

I think branching on the platform inside a larger script isn't great. Reusable workflows might work, but I am not familiar with them.

If we didn't have CI-specific workarounds, I think I would like to have a deps script for each platform and then source the right one. Unfortunately it seems that most of the files in this diff are full of stuff that is really specific to oddities of the proprietary CI infrastructure and I am not sure what to make of it.

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