runtime: Test failure: System.Tests.GCExtendedTests/TryStartNoGCRegion_SettingLatencyMode_ThrowsInvalidOperationException

Opened on behalf of @Jiayili1

The test System.Tests.GCExtendedTests/TryStartNoGCRegion_SettingLatencyMode_ThrowsInvalidOperationException has failed.

Assert.Equal() Failure\r Expected: 42\r Actual: -323331298

    Stack Trace:

       at xunit.console.netcore!<BaseAddress>+0x9a80cc
   at System.Tests.GCExtendedTests.TryStartNoGCRegion_SettingLatencyMode_ThrowsInvalidOperationException()
   at xunit.console.netcore!<BaseAddress>+0xb81531
   at SharedLibrary!<BaseAddress>+0x7626f3
   at SharedLibrary!<BaseAddress>+0x7624f3

Build : Master - 20170623.01 (UWP ILC Tests) Failing configurations:

Windows.10.Amd64.ClientRS3-x64
- Release

Detail: https://mc.dot.net/#/product/netcore/master/source/official~2Fcorefx~2Fmaster~2F/type/test~2Ffunctional~2Filc~2F/build/20170623.01/workItem/System.Runtime.Tests/analysis/xunit/System.Tests.GCExtendedTests~2FTryStartNoGCRegion_SettingLatencyMode_ThrowsInvalidOperationException

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 16 (16 by maintainers)

Most upvoted comments

Finally got a repro of this using the awesome Helix repro tool, and discovered that the cause of this issue is that the test requests only 1024 bytes of allocation room when entering the No GC region. Since the CoreRT runtime is mostly managed and allocates more than CoreCLR, this budget is not enough. I figure bumping up the budget by a few digits should work well in reducing the flakiness of this test. I will have a PR out for that shortly.

swgillespie on Jul 7, 2017

Will follow up offline with @swgillespie so that he can get a repro.

joperezr on Jul 5, 2017