Skip to content
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.

Sign up for GitHub

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

Jump to bottom

CI broken for windows-2022 builds #906

Closed
csciguy8 opened this issue Jun 11, 2024 · 2 comments · Fixed by #907
Closed

CI broken for windows-2022 builds #906

csciguy8 opened this issue Jun 11, 2024 · 2 comments · Fixed by #907
Assignees
@csciguy8

Comments

@csciguy8
Copy link
Contributor

See this run.

Most likely caused by this issue
@csciguy8
Copy link
Contributor Author

csciguy8 commented Jun 11, 2024 •
edited
Loading

I'm going to try to work around this by linking the VC runtime statically for unit tests
(similar to this issue comment)

@csciguy8 csciguy8 self-assigned this Jun 11, 2024
@csciguy8 csciguy8 mentioned this issue Jun 11, 2024
Merged
@csciguy8
Copy link
Contributor Author

Closing this issue as it appears resolved by Github.

I'm seeing successful windows-2022 builds as of yesterday, like this one.

They look to be using an updated runner image version Version: 20240610.1.0 compared to the broken builds that had Version: 20240603.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@csciguy8 csciguy8

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add support for static linking with MSVC runtime library CesiumGS/cesium-native
1 participant
@csciguy8