-
Notifications
You must be signed in to change notification settings - Fork 15
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
Replace Windows CI workflow with #165 #166
Conversation
this may be slow, but will avoid double zipping in the .zip (but not for the .nupkg, alas)
980a72b
to
7ed31d4
Compare
uses: actions/checkout@v4 | ||
with: | ||
sparse-checkout: src\3d\tests | ||
path: ${{ github.workspace }}\everparse |
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.
I think you may not need all the github.workspace
mentions here, it should be the directory where the runner is currently at. This is not so in the self-hosted runner only due to using a --login
shell, I think.
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 for your remark. However, I remember having issues with relative paths, so I inserted those absolute paths in a47be5e. I believe using explicit paths like those help maintaining the workflow and avoid relying on implicit knowledge of who works where.
The old Windows CI workflow was relying on a full build of F* from scratch, which is (currently) not possible on Windows. So, we need to disable it, and to replace it with the workflow that @mtzguido introduced in #165 and that builds a F* source package on Linux (or downloads a cached one) and then compiles that source package on Windows with EverParse.