Closed
Description
openedon Jan 31, 2022
On net7.0-Linux-Release-x64-CoreCLR_checked-Ubuntu.1804.Amd64.Open, System.Security.Cryptography.Tests failed with assertion:
+ ./RunTests.sh --runtime-path /datadisks/disk1/work/A40508DF/p
----- start Sun Jan 30 21:07:36 UTC 2022 =============== To repro directly: =====================================================
pushd .
/datadisks/disk1/work/A40508DF/p/dotnet exec --runtimeconfig System.Security.Cryptography.Tests.runtimeconfig.json --depsfile System.Security.Cryptography.Tests.deps.json xunit.console.dll System.Security.Cryptography.Tests.dll -xml testResults.xml -nologo -nocolor -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
popd
===========================================================================================================
/datadisks/disk1/work/A40508DF/w/A07A0890/e /datadisks/disk1/work/A40508DF/w/A07A0890/e
Assert failure(PID 28466 [0x00006f32], Thread: 28472 [0x6f38]): fieldSize != (unsigned int)-1
File: /__w/1/s/src/coreclr/vm/methodtable.cpp Line: 2323
Image: /datadisks/disk1/work/A40508DF/p/dotnet
./RunTests.sh: line 162: 28466 Aborted (core dumped) "$RUNTIME_PATH/dotnet" exec --runtimeconfig System.Security.Cryptography.Tests.runtimeconfig.json --depsfile System.Security.Cryptography.Tests.deps.json xunit.console.dll System.Security.Cryptography.Tests.dll -xml testResults.xml -nologo -nocolor -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing $RSP_FILE
/datadisks/disk1/work/A40508DF/w/A07A0890/e
----- end Sun Jan 30 21:07:38 UTC 2022 ----- exit code 134 ----------------------------------------------------------
exit code 134 means SIGABRT Abort. Managed or native assert, or runtime check such as heap corruption, caused call to abort(). Core dumped.
ulimit -c value: unlimited
The failure appears to be nondeterministic as the prior and subsequent rolling builds passed (and did not contain changes that would affect this, to my knowledge).
@bartonjs who would be the best person to investigate this?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment