-
Notifications
You must be signed in to change notification settings - Fork 14.3k
[libc++] Use GitHub-provided runners for the windows CI #79326
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -155,6 +155,9 @@ set(LLVM_COMPILER_CHECKED ON) | |
include(AddLLVM) | ||
include(HandleLLVMOptions) | ||
|
||
# Loot at the PATH first to avoid a version mismatch between the command-line | ||
# python and the CMake-found version | ||
set(Python3_FIND_REGISTRY LAST) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. FYI - ideally we wouldn't need to have things like this in the main CMakeLists.txt. Ideally we'd set it in the CI environment, as we happen to need it there due to how the Github runners are set up. It is possible to pass this on the CMake command line, I think, like On the other hand - this doesn't really hurt either; the cmake default behaviour is really really surprising here, and this makes it less surprising. It makes things a little inconsistent to keep setting this in the Anyway, just venting my thoughts on the matter - no urgent action needed. |
||
find_package(Python3 REQUIRED COMPONENTS Interpreter) | ||
|
||
# Host triple is used by tests to check if they are running natively. | ||
|
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.
When we're ready to merge this, we should add
needs: [ stage1, stage2, stage3 ]
to only trigger the Windows CI if the other stages are happy.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'd rather only wait for stage1, since the GitHub-provided agents are quite slow. I think it's quite unlikely that we'll actually hit resource limits, since we have up to 60 concurrent agents available, i.e. more than 7 libc++ patches uploaded in an hour that don't fail on stage1. We can still put that higher later if we do hit limitations at some point.