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.

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

ci: Switch GitHub Action's MSVC build to supported OS version #644

Merged
merged 1 commit into from
Apr 9, 2022

Conversation

striezel
Copy link
Contributor

@striezel striezel commented Apr 8, 2022

Description

The Windows-2016 environment for GitHub Actions has been retired in March 2022, so it's not available anymore. For further information on that see actions/runner-images#4312. However, we can test on the newer Windows 2022 environment instead. This also brings Visual Studio 2022.

So this pull request removes the GitHub Actions job using the Windows 2016 environment and introduces a new one with the Windows 2022 environment.

References

See actions/runner-images#4312 for the removal announcement of the windows-2016 environment.

Tasklist

  • Check that the new CI build with windows-2022 passes
  • Review and approve

Windows 2016 has been retired in March 2022, so it's not available
anymore. For further information on that see
<actions/runner-images#4312>.

However, we can test on the newer Windows 2022 image instead.
This also brings Visual Studio 2022.
@striezel
Copy link
Contributor Author

striezel commented Apr 9, 2022

Hmm...

Geralt_Hmm

The new MSVC 14.3 build (Visual Studio 2022) failed, but so did the existing MSVC 14.2 build (Visual Studio 2019). Unfortunately, that does not really give us any idea whether this new build is any good. So technically, this PR replaces a build that refuses to start due to removed build environment with a failing build on a newer build environment. But at least it's one step towards testing with newer MSVC version.

I am not really sure whether this is an improvement, though.
@mloskot: If you feel that it's not, then just feel free to close this PR without merging it. It's probably time that somebody looked into the build failures with MSVC more closely, but unfortunately I do neither have the time nor the proper development environment to do this at the moment.

@mloskot
Copy link
Member

mloskot commented Apr 9, 2022

The new MSVC 14.3 build (Visual Studio 2022) failed, but so did the existing MSVC 14.2 build (Visual Studio 2019).

I've just pushed this cf1e6b1 which hopefully fix the failures (as far as I've checked them). Please, update your PR and let's see if it helps.

It's probably time that somebody looked into the build failures with MSVC more closely, but unfortunately I do neither have the time nor the proper development environment to do this at the moment.

No worries, I will look into the build/test failures. Your CI improvements are very helpful, even if not complete as Every Little Helps :)

Copy link
Member

@mloskot mloskot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is fine to merge w/o updating.

@mloskot mloskot merged commit 09c3464 into boostorg:develop Apr 9, 2022
@striezel striezel deleted the ci-update-msvc branch April 9, 2022 11:59
@mloskot mloskot mentioned this pull request May 12, 2022
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants