-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Toolset update: VS 2022 17.7 Preview 2 #3769
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…noexcept dtor when a data member has a throwing dtor".
…cifiers of hidden friend functions are complete-class contexts".
…xpansion to repeat a type N times".
* azure-pipelines.yml: + Reduce the timeout for Code Format Validation from 20 min to 5 min. This is still a ~5x safety margin as it takes ~56 seconds total. * azure-devops/cmake-configure-build.yml: + Reduce the timeout for building the STL from 10 min to 5 min. This is still a ~3x safety margin as it takes ~1m 43s to build. + Reduce the timeout for building the benchmarks from 10 min to 2 min. This is a massive safety margin as it takes ~5s to build. * azure-devops/run-tests.yml: + Reduce the timeout for actually running the tests from 120 min to 20 min. This is still a ~2x safety margin as the tests currently take ~8m 24s to run for the slowest slice. + Reduce the timeout for publishing the tests for 10 min to 5 min. This is a massive safety margin as it takes ~11s to publish, although it may be network-dependent, hence the caution. * azure-devops/cross-build.yml: * azure-devops/native-build-test.yml: + Reduce the overall timeouts from 360 minutes to 25 minutes. This gives us a ~2x safety margin, as the tests typically finish in ~12 min, and are virtually guaranteed to be doomed if they've run for over 15 minutes.
CaseyCarter
approved these changes
Jun 14, 2023
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
…a pack expansion to repeat a type N times"." This reverts commit 34535b0.
I had to restore the workaround for VSO-1761088 "ICE when using a pack expansion to repeat a type N times" because the MSVC-internal build is using a 17.6-based compiler, whereas this bug was fixed in 17.7p1. I'll try again in a later PR. |
CaseyCarter
approved these changes
Jun 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
noexcept
dtor when a data member has a throwing dtor".noexcept
-specifiers of hidden friend functions are complete-class contexts".azure-pipelines.yml
:azure-devops/cmake-configure-build.yml
:azure-devops/run-tests.yml
:azure-devops/cross-build.yml
:azure-devops/native-build-test.yml
: