-
Notifications
You must be signed in to change notification settings - Fork 199
Fix Windows GitHub CI #977
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
Fix Windows GitHub CI #977
Conversation
- Use windows-2019 image - Use prebuilt LLVM 15 - Build boost in CI
In the Github runner, another LLVM is installed in C:\Program Files, we want to use the prebuilt one
TODO: Check if this is still necessary and how to make it work with LLVM13+
Required for symbols from LLVM CommandLine library
Re the |
When compiling the tests with the CUDA backend, we're getting errors that have been fixed in for Visual Studio 2022 here: microsoft/STL#2075
ef76c48
to
35e6582
Compare
The prebuilt LLVM was not build with CUDA enabled
In fact, this is not available in LLVM 11 (only when patched with https://reviews.llvm.org/D69322) but the prebuilt LLVM in CI is exactly a patched LLVM 11.
Maybe @fodinabor can have a look at this? |
@fodinabor are you still planning to look at this? If not it's fine, I'd just like to merge this soonish as it should be a massive quality of life improvement once contributors are no longer spammed with emails about Windows CI failures :-) |
Sorry for the delay... |
Thanks for the feedback!
yikes... That means that basic code has the chance of blowing up, not even talking about data structures.. even |
This PR fixes the Windows CI.
There are still a few TODOs (but at least the CPU tests compile):
setDeviceMangleContext
does not exist in LLVM 15 (I think it was removed in LLVM13). Maybe @fodinabor knows if it is fine to just remove this?Compilation of tests with CUDAAdd more CUDA versionsEdit: Just compiling and running the tests for CPU for now