Repository navigation
Test failure: Microsoft.Extensions.Caching.Memory.CapacityTests.DoNotAddIfSizeOverflows #39241
Description
Windows, x86, COMPlus_JitStressRegs=8
I don't think this is related to JitStressRegs; I can't repro it locally like that. I think the test simply fails sometimes on loaded systems due to this code:
// Wait for compaction to complete
Assert.True(await sem.WaitAsync(TimeSpan.FromSeconds(10)));
Kusto shows 6 such failures in the last 30 days (all Windows x86, JitStress).
Could this timeout number be made much, much higher?
Activity
danmoseley commentedon Jul 14, 2020
Increasing the timeout would not affect tests that pass today, right? I think it would be fine if you want to increase those numbers.
BruceForstall commentedon Jul 14, 2020
No idea. That would be up to the test owner to determine.
I would prefer the test/area owner make that change, to contribute to a better, more stable CI.
BruceForstall commentedon Jul 18, 2020
Failed again:
https://dev.azure.com/dnceng/public/_build/results?buildId=736732&view=ms.vss-test-web.build-test-results-tab&runId=22818708&resultId=102444&paneView=debug
BruceForstall commentedon Jul 26, 2020
Failed again: https://dev.azure.com/dnceng/public/_build/results?buildId=746053&view=ms.vss-test-web.build-test-results-tab&runId=23124036&resultId=102773&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab
BruceForstall commentedon Jul 26, 2020
Dup'ing to #33993
Disable Microsoft.Extensions.Caching.Memory.CapacityTests.DoNotAddIfS…
Disable Microsoft.Extensions.Caching.Memory.CapacityTests.DoNotAddIfS…
Disable Microsoft.Extensions.Caching.Memory.CapacityTests.DoNotAddIfS…