catch is evidently incompatible with VS 2022 (platform toolset v143) - backing off to unblock #1127
Conversation
This file contains hidden or 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
…- backing off to unblock
Contributor
|
I don't see anything in catch's issue tracker that suggests it doesn't work with VS 2022 - what issue are we seeing here? |
Member
Author
|
@sylveon Me neither, but backing off to the 142 toolset appears to be a reliable workaround. Issues we're seeing are occasional crashes of the test binaries ("SIGSEGV - Segmentation violation signal") across random test cases. |
Contributor
|
Ah, I've been seeing those too but just scratched it off to my computer being weird since AzDO was running tests fine. |
Member
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Looked at latest version of catch, 2.13.8, and saw no significant differences from 2.13.7 (checked in here) to suggest that would help. So backing test collateral off to platform toolset v142 (VS1029) to unblock build for now.