Closed VSadov closed 1 year ago
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas See info in area-owners.md if you want to be subscribed.
Author: | VSadov |
---|---|
Assignees: | - |
Labels: | `area-NativeAOT-coreclr` |
Milestone: | - |
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch, @kunalspathak See info in area-owners.md if you want to be subscribed.
Author: | VSadov |
---|---|
Assignees: | - |
Labels: | `area-CodeGen-coreclr`, `untriaged`, `area-NativeAOT-coreclr` |
Milestone: | - |
I will disable the offending test. Just need to be sure it is the only one affected.
This must be a relatively recent issue. I run tests with chk runtime frequently and did not see it. However my base (5d88ff404de77d78e07ad3de7fa2af270332da22) was a few days old. The issue must be newer than that commit.
This is the only test affected. With System.Net.Sockets.Tests
excluded chk/ret NativeAOT Libraries tests pass locally.
@VSadov can you please remind me how do I build a specific BCL test suite with NAOT? I think last time I tried it only worked for the whole BCL suite and took several hours
I think last time I tried it only worked for the whole BCL suite and took several hours
I takes about 12-15 minutes to run the whole suite on AMD 5950X from clean state, so it is not too bad. I run the whole suite fairly often. It does need a fast machine with lots of memory though.
There were some instructions for selective compiling/running tests in https://github.com/dotnet/runtime/issues/78717
build.cmd -s clr.aot+libs -rc checked -c Release
cd src\libraries\System.Net.Sockets\tests\FunctionalTests
..\..\..\..\..\dotnet.cmd build /t:Test -c Release /p:TestNativeAot=true /p:CoreCLRConfiguration=checked
@EgorBo - FYI. The test has been disabled on NativeAOT in https://github.com/dotnet/runtime/pull/84114. If you decide to run the whole suite, you'd need to sync to before that change.
(also if you decide to run the whole suite on your new machine 🚀, do share how long it took. ;)