-
Notifications
You must be signed in to change notification settings - Fork 300
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
Temporary update to LLVM 16 on Windows #1079
Conversation
7d42332
to
a7cb1f4
Compare
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.
Assuming the experiment works, this LGTM
Need to up my foo with the yaml here, fingers crossed.
…On Tue, Aug 29, 2023 at 3:32 PM James M Snell ***@***.***> wrote:
***@***.**** approved this pull request.
Assuming the experiment works, this LGTM
—
Reply to this email directly, view it on GitHub
<#1079 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABACZOWYUATHKZ2MY2X3XUTXXX4O3ANCNFSM6AAAAAA4C7F3K4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Github action language...my PR here breaks Linux / Mac which then fail before the Windows build can get going...would like to specialize the execution flow for Windows vs Unix...it's going to be trivial once you know the runes... |
c42b1b7
to
12a23e5
Compare
Issue is actions/runner-images#8125 (comment) |
58aa182
to
acaf3fb
Compare
acaf3fb
to
b3c3267
Compare
Still failing with LLVM 16:
|
Looks similar to #41, adding test.yml to the files hashed for the cache to invalidate it. |
e375991
to
0de0d83
Compare
Recent github runner config changes for Windows breaks use of LLVM 15 and does not install LLVM 16 in the image. This change adds an LLVM upgrade step that should pull in LLVM 16. This follows scikit-image/scikit-image#7109. Bug: actions/runner-images#812
0de0d83
to
ba49f32
Compare
From experimenting locally at home, this issue repros perfectly after upgrading to LLVM 16 ( The underlying problem with LLVM 16 has been reported here: Renaming
|
Dropping this in favour of #1092 |
No description provided.