Repository navigation
ManyConcurrentAddsTakes_ForceContentionWithToArray fails intermittently on osx-arm64 #76501
Copy link
Copy link
Closed
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarch-arm64area-System.Collectionsos-macosmacOS aka OSXmacOS aka OSXtenet-reliabilityReliability/stability related issue (stress, load problems, etc.)Reliability/stability related issue (stress, load problems, etc.)test-failure
Milestone
Description
Assert.DoesNotContain() Failure
Found: 0
In value: Int32[] [0]
at System.Collections.Concurrent.Tests.ProducerConsumerCollectionTests.ManyConcurrentAddsTakes_ForceContentionWithToArray(Double seconds) + 0x110
at System.Collections.Concurrent!<BaseAddress>+0x9fa6bc
at System.Reflection.DynamicInvokeInfo.Invoke(Object, IntPtr, Object[], BinderBundle, Boolean) + 0x148
{
"ErrorMessage" : "System.Collections.Concurrent.Tests.ProducerConsumerCollectionTests.ManyConcurrentAddsTakes_ForceContentionWithToArray",
"BuildRetry": false
}Failed in #76499. Log: https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-76499-merge-3c4c964d671349bdbd/System.Collections.Concurrent.Tests/1/console.b1cceddc.log?helixlogtype=result
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 5 | 12 |
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarch-arm64area-System.Collectionsos-macosmacOS aka OSXmacOS aka OSXtenet-reliabilityReliability/stability related issue (stress, load problems, etc.)Reliability/stability related issue (stress, load problems, etc.)test-failure
Activity
jkotas commentedon Oct 2, 2022
Also failed in #75421 (comment)
jkotas commentedon Oct 2, 2022
cc @VSadov @filipnavara
filipnavara commentedon Oct 2, 2022
I believe the failure is genuine but I was not able to reliably reproduce it on my machine yet. Should we mark the test with
ActiveIssueuntil we find the root cause?jkotas commentedon Oct 2, 2022
"Known Build Error" label turns on automation to monitor and collect statistics about the failure. Let's see how often it fails. If it fails too often, we are going to disable it.
filipnavara commentedon Oct 4, 2022
It reproduces in less than a minute when running the single test in loop on M1.
filipnavara commentedon Oct 4, 2022
In fact, it reproduces under regular CoreCLR as well:
ConcurrentDict.cs:
filipnavara commentedon Oct 4, 2022
Note that the failure is also reproducible on 7.0 RC1 so it may be appropriate to change the milestone.
[-][NativeAOT] ManyConcurrentAddsTakes_ForceContentionWithToArray fails intermittently on osx-arm64[/-][+]ManyConcurrentAddsTakes_ForceContentionWithToArray fails intermittently on osx-arm64[/+]akoeplinger commentedon Oct 4, 2022
Might be related: #76141
filipnavara commentedon Oct 4, 2022
Likely not, I already checked the existing issues. This one is
ConcurrentQueueand the other one isConcurrentStack.VSadov commentedon Nov 10, 2022
Looks like an ordering issue on arm64. I will take a look
VSadov commentedon Nov 10, 2022
I am able to reproduce this on OSX-arm64-CoreCLR
VSadov commentedon Nov 10, 2022
PR with a fix: #78142
I am running the repro in multiple processes for about 20 min now with no failures. It typically fails in under one minute.