You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Build: 🔎https://dev.azure.com/dnceng-public/public/_build/results?buildId=984942 Error message validated:[[Long Running Test] 'System.Composition.UnitTests.ConcurrencyTests.SharedInstancesAreNotVisibleUntilActivationCompletes'] Result validation: ✅ Known issue matched with the provided build. Validation performed at: 3/19/2025 12:38:53 PM UTC
The code in System.Composition has not changed except for #113667 which "updates the target .NET Framework version from net48 to net481 in pipelines, tests, and documentation to meet the requirements for consuming xUnit v3." and that appears to be been added 1 day after the first reported test failure.
This test has been failing continuously since March 19, 2025 — nearly a full year of uninterrupted flakiness. It has never dropped to 0/0/0 hit counts (one single failure period). It's been quieter recently (last failure 33 days ago) but hasn't formally cleared.
Activity
dotnet-policy-service commentedon Mar 19, 2025
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.
dotnet-policy-service commentedon Mar 19, 2025
Tagging subscribers to this area: @dotnet/area-system-composition
See info in area-owners.md if you want to be subscribed.
steveharter commentedon Mar 24, 2025
Sample log:
steveharter commentedon Mar 24, 2025
The test has not been modified.
The code in System.Composition has not changed except for #113667 which "updates the target .NET Framework version from net48 to net481 in pipelines, tests, and documentation to meet the requirements for consuming xUnit v3." and that appears to be been added 1 day after the first reported test failure.
jeffschwMSFT commentedon Mar 18, 2026
removing blocking-clean-ci as it has not failed in 30 days
danmoseley commentedon Mar 22, 2026
Note
This comment was AI/Copilot-generated.
Known Issue Failure History
Analysis of edit history on this issue (via known-issue-history skill):
This test has been failing continuously since March 19, 2025 — nearly a full year of uninterrupted flakiness. It has never dropped to 0/0/0 hit counts (one single failure period). It's been quieter recently (last failure 33 days ago) but hasn't formally cleared.