{{ message }}
Categorize some threading libc++ test skip#6073
Merged
StephanTLavavej merged 1 commit intoFeb 11, 2026
Merged
Conversation
StephanTLavavej
approved these changes
Feb 5, 2026
Member
Member
|
I'm mirroring this to the MSVC-internal repo. Please notify me if any further changes are pushed, otherwise no action is required. |
Member
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
atomic_reffailures are one well know annoying problem; [lib++][test] Alignatomic_refunderlying variable as required llvm/llvm-project#179780 is merged.futurefailure is <future>: incorrectly used copy assignment instead of copy construction in set_value #1190 (<future>:promisedefault constructs the value type #2488 is the same problem described from a different angle)