dotnet / runtime

.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
https://docs.microsoft.com/dotnet/core/
MIT License
15.28k stars 4.74k forks source link

System.Security.Cryptography.X509Certificates.Tests crashing on Mariner OS #57810

Open ViktorHofer opened 3 years ago

ViktorHofer commented 3 years ago

Configuration: net6.0-Linux-Release-x64-Mono_release-(Mariner.1.0.Amd64.Open)ubuntu.1604.amd64.open@mcr.microsoft.com/dotnet-buildtools/prereqs:cbl-mariner-1.0-helix-20210528192219-92bf620

Console log: https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-9ceea0655ec846a0a6/System.Security.Cryptography.X509Certificates.Tests/1/console.10f1c92f.log?sv=2019-07-07&se=2021-09-07T08%3A33%3A20Z&sr=c&sp=rl&sig=HoZ9NO4K4w0Q%2BVf69HSt5eWYYCzqxtmOWEYPN68vdQ4%3D

Build: https://dev.azure.com/dnceng/public/_build/results?buildId=1300925&view=ms.vss-test-web.build-test-results-tab&runId=38340862&resultId=100247&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab

  Discovering: System.Security.Cryptography.X509Certificates.Tests (method display = ClassAndMethod, method display options = None)
  Discovered:  System.Security.Cryptography.X509Certificates.Tests (found 565 of 704 test cases)
  Starting:    System.Security.Cryptography.X509Certificates.Tests (parallel test collections = on, max threads = 2)

=================================================================
    Native Crash Reporting
=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================

=================================================================
    Native stacktrace:
=================================================================
    0x7fec0fc7f6c0 - Unknown
    0x7fec0fc249de - Unknown
    0x7fec0fb88b35 - Unknown
    0x7fec104527e0 - Unknown
    0x7fec059a9bd4 - Unknown
    0x7fec059c63d3 - Unknown
    0x7fec05874fa8 - Unknown
    0x7fec05874c7f - Unknown
    0x7fec05874fa8 - Unknown
    0x7fec05874c7f - Unknown
    0x7fec05874ec9 - Unknown
    0x41eeb20b - Unknown

=================================================================
    Telemetry Dumper:
=================================================================
Pkilling 0x140651694896896x from 0x140651813463808x
Pkilling 0x140651677824768x from 0x140651813463808x
Pkilling 0x140651673249536x from 0x140651813463808x
Pkilling 0x140651794736896x from 0x140651813463808x
Pkilling 0x140651815565056x from 0x140651813463808x
Pkilling 0x140651675350784x from 0x140651813463808x
Pkilling 0x140651678091008x from 0x140651813463808x
Pkilling 0x140651856201536x from 0x140651813463808x
Pkilling 0x140651792635648x from 0x140651813463808x
Entering thread summarizer pause from 0x140651813463808x
Could not exec mono-hang-watchdog, expected on path '/__w/1/s/artifacts/obj/mono/Linux.x64.Release/out/etc/../bin/mono-hang-watchdog' (errno 2)
Finished thread summarizer pause from 0x140651813463808x.
Failed to create breadcrumb file (null)/crash_hash_0x31412640a

Waiting for dumping threads to resume

=================================================================
    External Debugger Dump:
=================================================================
mono_gdb_render_native_backtraces not supported on this platform, unable to find gdb or lldb

=================================================================
    Basic Fault Address Reporting
=================================================================
Memory around native instruction pointer (0x7fec059a9bd4):0x7fec059a9bc4  7e 23 49 89 f4 31 db 0f 1f 44 00 00 48 8b 45 08  ~#I..1...D..H.E.
0x7fec059a9bd4  48 8b 3c d8 48 85 ff 74 03 41 ff d4 48 83 c3 01  H.<.H..t.A..H...
0x7fec059a9be4  39 5d 00 7f e7 5b 48 89 ef 5d 41 5c e9 7b fc ff  9]...[H..]A\.{..
0x7fec059a9bf4  ff 0f 1f 00 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa  ................

=================================================================
    Managed Stacktrace:
=================================================================
      at <unknown> <0xffffffff>
      at Crypto:X509Destroy <0x000aa>
      at Microsoft.Win32.SafeHandles.SafeX509Handle:ReleaseHandle <0x0002f>
      at System.Runtime.InteropServices.SafeHandle:InternalRelease <0x0011c>
      at System.Runtime.InteropServices.SafeHandle:Dispose <0x0002f>
      at System.Runtime.InteropServices.SafeHandle:Finalize <0x0003e>
      at System.Object:runtime_invoke_virtual_void__this__ <0x0008c>
=================================================================
./RunTests.sh: line 162:    24 Aborted                 (core dumped) "$RUNTIME_PATH/dotnet" exec --runtimeconfig System.Security.Cryptography.X509Certificates.Tests.runtimeconfig.json --depsfile System.Security.Cryptography.X509Certificates.Tests.deps.json xunit.console.dll System.Security.Cryptography.X509Certificates.Tests.dll -xml testResults.xml -nologo -nocolor -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing $RSP_FILE
/root/helix/work/workitem
----- end Wed Aug 18 08:51:53 UTC 2021 ----- 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
[   57.327326] Bridge firewalling registered
[   57.787706] Initializing XFRM netlink socket
[   57.837719] Netfilter messages via NETLINK v0.30.
[   57.881827] ctnetlink v0.93: registering with nfnetlink.
[   57.999630] IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
[  125.108971] docker0: port 1(vethf993294) entered blocking state
[  125.108973] docker0: port 1(vethf993294) entered disabled state
[  125.109590] device vethf993294 entered promiscuous mode
[  125.109652] IPv6: ADDRCONF(NETDEV_UP): vethf993294: link is not ready
[  153.495273] cgroup: cgroup: disabling cgroup2 socket matching due to net_prio or net_cls activation
[  153.675572] eth0: renamed from veth25e3a73
[  153.734363] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  153.736603] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  153.736619] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  153.736636] IPv6: ADDRCONF(NETDEV_CHANGE): vethf993294: link becomes ready
[  153.736650] docker0: port 1(vethf993294) entered blocking state
[  153.736652] docker0: port 1(vethf993294) entered forwarding state
[  153.736676] IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
[  158.244680] docker0: port 1(vethf993294) entered disabled state
[  158.244720] veth25e3a73: renamed from eth0
[  161.040789] docker0: port 1(vethf993294) entered disabled state
[  161.041952] device vethf993294 left promiscuous mode
[  161.041954] docker0: port 1(vethf993294) entered disabled state
[  240.752031] docker0: port 1(veth0ed58bd) entered blocking state
[  240.752033] docker0: port 1(veth0ed58bd) entered disabled state
[  240.752073] device veth0ed58bd entered promiscuous mode
[  240.752122] IPv6: ADDRCONF(NETDEV_UP): veth0ed58bd: link is not ready
[  241.072313] eth0: renamed from vethbdda377
[  241.122064] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  241.123620] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  241.123630] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  241.123648] IPv6: ADDRCONF(NETDEV_CHANGE): veth0ed58bd: link becomes ready
[  241.123666] docker0: port 1(veth0ed58bd) entered blocking state
[  241.123667] docker0: port 1(veth0ed58bd) entered forwarding state
[  242.778177] docker0: port 1(veth0ed58bd) entered disabled state
[  242.778206] vethbdda377: renamed from eth0
[  242.851178] docker0: port 1(veth0ed58bd) entered disabled state
[  242.852132] device veth0ed58bd left promiscuous mode
[  242.852134] docker0: port 1(veth0ed58bd) entered disabled state
[  248.655239] docker0: port 1(vethab83ccb) entered blocking state
[  248.655241] docker0: port 1(vethab83ccb) entered disabled state
[  248.655280] device vethab83ccb entered promiscuous mode
[  248.655328] IPv6: ADDRCONF(NETDEV_UP): vethab83ccb: link is not ready
[  248.916219] eth0: renamed from veth82699b2
[  248.960569] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  248.962024] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  248.962034] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  248.962051] IPv6: ADDRCONF(NETDEV_CHANGE): vethab83ccb: link becomes ready
[  248.962068] docker0: port 1(vethab83ccb) entered blocking state
[  248.962070] docker0: port 1(vethab83ccb) entered forwarding state
Waiting a few seconds for any dump to be written..
cat /proc/sys/kernel/core_pattern: /home/helixbot/dotnetbuild/dumps/core.%u.%p
cat /proc/sys/kernel/core_uses_pid: 0
cat: /proc/sys/kernel/coredump_filter: No such file or directory
cat /proc/sys/kernel/coredump_filter:
Looking around for any Linux dump..
... found no dump in /root/helix/work/workitem
+ export _commandExitCode=134
+ _commandExitCode=134

cc @danmoseley @safern @marek-safar

dotnet-issue-labeler[bot] commented 3 years ago

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

ghost commented 3 years ago

Tagging subscribers to this area: @bartonjs, @vcsjones, @krwq, @GrabYourPitchForks See info in area-owners.md if you want to be subscribed.

Issue Details
Configuration: `net6.0-Linux-Release-x64-Mono_release-(Mariner.1.0.Amd64.Open)ubuntu.1604.amd64.open@mcr.microsoft.com/dotnet-buildtools/prereqs:cbl-mariner-1.0-helix-20210528192219-92bf620` Console log: https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-9ceea0655ec846a0a6/System.Security.Cryptography.X509Certificates.Tests/1/console.10f1c92f.log?sv=2019-07-07&se=2021-09-07T08%3A33%3A20Z&sr=c&sp=rl&sig=HoZ9NO4K4w0Q%2BVf69HSt5eWYYCzqxtmOWEYPN68vdQ4%3D Build: https://dev.azure.com/dnceng/public/_build/results?buildId=1300925&view=ms.vss-test-web.build-test-results-tab&runId=38340862&resultId=100247&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab ``` Discovering: System.Security.Cryptography.X509Certificates.Tests (method display = ClassAndMethod, method display options = None) Discovered: System.Security.Cryptography.X509Certificates.Tests (found 565 of 704 test cases) Starting: System.Security.Cryptography.X509Certificates.Tests (parallel test collections = on, max threads = 2) ================================================================= Native Crash Reporting ================================================================= Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= ================================================================= Native stacktrace: ================================================================= 0x7fec0fc7f6c0 - Unknown 0x7fec0fc249de - Unknown 0x7fec0fb88b35 - Unknown 0x7fec104527e0 - Unknown 0x7fec059a9bd4 - Unknown 0x7fec059c63d3 - Unknown 0x7fec05874fa8 - Unknown 0x7fec05874c7f - Unknown 0x7fec05874fa8 - Unknown 0x7fec05874c7f - Unknown 0x7fec05874ec9 - Unknown 0x41eeb20b - Unknown ================================================================= Telemetry Dumper: ================================================================= Pkilling 0x140651694896896x from 0x140651813463808x Pkilling 0x140651677824768x from 0x140651813463808x Pkilling 0x140651673249536x from 0x140651813463808x Pkilling 0x140651794736896x from 0x140651813463808x Pkilling 0x140651815565056x from 0x140651813463808x Pkilling 0x140651675350784x from 0x140651813463808x Pkilling 0x140651678091008x from 0x140651813463808x Pkilling 0x140651856201536x from 0x140651813463808x Pkilling 0x140651792635648x from 0x140651813463808x Entering thread summarizer pause from 0x140651813463808x Could not exec mono-hang-watchdog, expected on path '/__w/1/s/artifacts/obj/mono/Linux.x64.Release/out/etc/../bin/mono-hang-watchdog' (errno 2) Finished thread summarizer pause from 0x140651813463808x. Failed to create breadcrumb file (null)/crash_hash_0x31412640a Waiting for dumping threads to resume ================================================================= External Debugger Dump: ================================================================= mono_gdb_render_native_backtraces not supported on this platform, unable to find gdb or lldb ================================================================= Basic Fault Address Reporting ================================================================= Memory around native instruction pointer (0x7fec059a9bd4):0x7fec059a9bc4 7e 23 49 89 f4 31 db 0f 1f 44 00 00 48 8b 45 08 ~#I..1...D..H.E. 0x7fec059a9bd4 48 8b 3c d8 48 85 ff 74 03 41 ff d4 48 83 c3 01 H.<.H..t.A..H... 0x7fec059a9be4 39 5d 00 7f e7 5b 48 89 ef 5d 41 5c e9 7b fc ff 9]...[H..]A\.{.. 0x7fec059a9bf4 ff 0f 1f 00 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa ................ ================================================================= Managed Stacktrace: ================================================================= at <0xffffffff> at Crypto:X509Destroy <0x000aa> at Microsoft.Win32.SafeHandles.SafeX509Handle:ReleaseHandle <0x0002f> at System.Runtime.InteropServices.SafeHandle:InternalRelease <0x0011c> at System.Runtime.InteropServices.SafeHandle:Dispose <0x0002f> at System.Runtime.InteropServices.SafeHandle:Finalize <0x0003e> at System.Object:runtime_invoke_virtual_void__this__ <0x0008c> ================================================================= ./RunTests.sh: line 162: 24 Aborted (core dumped) "$RUNTIME_PATH/dotnet" exec --runtimeconfig System.Security.Cryptography.X509Certificates.Tests.runtimeconfig.json --depsfile System.Security.Cryptography.X509Certificates.Tests.deps.json xunit.console.dll System.Security.Cryptography.X509Certificates.Tests.dll -xml testResults.xml -nologo -nocolor -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing $RSP_FILE /root/helix/work/workitem ----- end Wed Aug 18 08:51:53 UTC 2021 ----- 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 [ 57.327326] Bridge firewalling registered [ 57.787706] Initializing XFRM netlink socket [ 57.837719] Netfilter messages via NETLINK v0.30. [ 57.881827] ctnetlink v0.93: registering with nfnetlink. [ 57.999630] IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready [ 125.108971] docker0: port 1(vethf993294) entered blocking state [ 125.108973] docker0: port 1(vethf993294) entered disabled state [ 125.109590] device vethf993294 entered promiscuous mode [ 125.109652] IPv6: ADDRCONF(NETDEV_UP): vethf993294: link is not ready [ 153.495273] cgroup: cgroup: disabling cgroup2 socket matching due to net_prio or net_cls activation [ 153.675572] eth0: renamed from veth25e3a73 [ 153.734363] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 153.736603] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 153.736619] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 153.736636] IPv6: ADDRCONF(NETDEV_CHANGE): vethf993294: link becomes ready [ 153.736650] docker0: port 1(vethf993294) entered blocking state [ 153.736652] docker0: port 1(vethf993294) entered forwarding state [ 153.736676] IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready [ 158.244680] docker0: port 1(vethf993294) entered disabled state [ 158.244720] veth25e3a73: renamed from eth0 [ 161.040789] docker0: port 1(vethf993294) entered disabled state [ 161.041952] device vethf993294 left promiscuous mode [ 161.041954] docker0: port 1(vethf993294) entered disabled state [ 240.752031] docker0: port 1(veth0ed58bd) entered blocking state [ 240.752033] docker0: port 1(veth0ed58bd) entered disabled state [ 240.752073] device veth0ed58bd entered promiscuous mode [ 240.752122] IPv6: ADDRCONF(NETDEV_UP): veth0ed58bd: link is not ready [ 241.072313] eth0: renamed from vethbdda377 [ 241.122064] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 241.123620] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 241.123630] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 241.123648] IPv6: ADDRCONF(NETDEV_CHANGE): veth0ed58bd: link becomes ready [ 241.123666] docker0: port 1(veth0ed58bd) entered blocking state [ 241.123667] docker0: port 1(veth0ed58bd) entered forwarding state [ 242.778177] docker0: port 1(veth0ed58bd) entered disabled state [ 242.778206] vethbdda377: renamed from eth0 [ 242.851178] docker0: port 1(veth0ed58bd) entered disabled state [ 242.852132] device veth0ed58bd left promiscuous mode [ 242.852134] docker0: port 1(veth0ed58bd) entered disabled state [ 248.655239] docker0: port 1(vethab83ccb) entered blocking state [ 248.655241] docker0: port 1(vethab83ccb) entered disabled state [ 248.655280] device vethab83ccb entered promiscuous mode [ 248.655328] IPv6: ADDRCONF(NETDEV_UP): vethab83ccb: link is not ready [ 248.916219] eth0: renamed from veth82699b2 [ 248.960569] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 248.962024] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 248.962034] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 248.962051] IPv6: ADDRCONF(NETDEV_CHANGE): vethab83ccb: link becomes ready [ 248.962068] docker0: port 1(vethab83ccb) entered blocking state [ 248.962070] docker0: port 1(vethab83ccb) entered forwarding state Waiting a few seconds for any dump to be written.. cat /proc/sys/kernel/core_pattern: /home/helixbot/dotnetbuild/dumps/core.%u.%p cat /proc/sys/kernel/core_uses_pid: 0 cat: /proc/sys/kernel/coredump_filter: No such file or directory cat /proc/sys/kernel/coredump_filter: Looking around for any Linux dump.. ... found no dump in /root/helix/work/workitem + export _commandExitCode=134 + _commandExitCode=134 ``` cc @danmoseley @safern @marek-safar
Author: ViktorHofer
Assignees: -
Labels: `area-System.Security`, `os-mariner`
Milestone: -
vcsjones commented 3 years ago

Duplicate of https://github.com/dotnet/runtime/issues/57506?

ViktorHofer commented 3 years ago

Based on the stack trace this looks different. Don't see any Internal.Cryptography.Pal.ChainPal.BuildChain frames here.

ViktorHofer commented 3 years ago

Apparently https://github.com/dotnet/runtime/pull/57811 didn't help as the test assembly is still crashing on Mariner: https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-930b6759615d4fa38f/System.Security.Cryptography.X509Certificates.Tests/1/console.779c5cb4.log?sv=2019-07-07&se=2021-09-13T21%3A00%3A03Z&sr=c&sp=rl&sig=7FcvQL4ouNFNYbp2I3bei3dBiuaIBxQ3RD9TuPiumHA%3D.

Presumably the crash happens before the the assembly is skipped, during test discovery.

bartonjs commented 2 years ago

No longer repros:

root [ /projects/runtime/src/libraries/System.Security.Cryptography.X509Certificates/tests ]# ../../../../.dotnet/dotnet msbuild /t:Test /p:OuterLoop=true
MSBuild version 17.3.0-preview-22306-01+1c045cf58 for .NET
  Microsoft.Interop.SourceGeneration -> /projects/runtime/artifacts/bin/Microsoft.Interop.SourceGeneration/Debug/netstandard2.0/Microsoft.Interop.SourceGeneration.dll
  LibraryImportGenerator -> /projects/runtime/artifacts/bin/LibraryImportGenerator/Debug/netstandard2.0/Microsoft.Interop.LibraryImportGenerator.dll
  TestUtilities -> /projects/runtime/artifacts/bin/TestUtilities/Debug/net6.0/TestUtilities.dll
  System.Runtime -> /projects/runtime/artifacts/bin/System.Runtime/ref/Debug/net7.0/System.Runtime.dll
  System.Runtime.Numerics -> /projects/runtime/artifacts/bin/System.Runtime.Numerics/ref/Debug/net7.0/System.Runtime.Numerics.dll
  System.Collections -> /projects/runtime/artifacts/bin/System.Collections/ref/Debug/net7.0/System.Collections.dll
  System.Formats.Asn1 -> /projects/runtime/artifacts/bin/System.Formats.Asn1/ref/Debug/net7.0/System.Formats.Asn1.dll
  System.Formats.Asn1 -> /projects/runtime/artifacts/bin/System.Formats.Asn1/Debug/net7.0/System.Formats.Asn1.dll
  System.Security.Cryptography.Pkcs -> /projects/runtime/artifacts/bin/System.Security.Cryptography.Pkcs/ref/Debug/net7.0/System.Security.Cryptography.Pkcs.dll
  System.Security.Cryptography.Pkcs -> /projects/runtime/artifacts/bin/System.Security.Cryptography.Pkcs/Debug/net7.0/System.Security.Cryptography.Pkcs.dll
  System.Security.Cryptography.X509Certificates.Tests -> /projects/runtime/artifacts/bin/System.Security.Cryptography.X509Certificates.Tests/Debug/net7.0-unix/System.Security.Cryptography.X509Certificates.Tests.dll
  ----- start Fri Aug 5 05:27:13 PM UTC 2022 =============== To repro directly: =====================================================
  pushd /projects/runtime/artifacts/bin/System.Security.Cryptography.X509Certificates.Tests/Debug/net7.0-unix
  /projects/runtime/artifacts/bin/testhost/net7.0-Linux-Debug-x64/dotnet exec --runtimeconfig System.Security.Cryptography.X509Certificates.Tests.runtimeconfig.json --depsfile System.Security.Cryptography.X509Certificates.Tests.deps.json xunit.console.dll System.Security.Cryptography.X509Certificates.Tests.dll -xml testResults.xml -nologo -notrait category=failing
  popd
  ===========================================================================================================
  /projects/runtime/artifacts/bin/System.Security.Cryptography.X509Certificates.Tests/Debug/net7.0-unix /projects/runtime/src/libraries/System.Security.Cryptography.X509Certificates/tests
    Discovering: System.Security.Cryptography.X509Certificates.Tests (method display = ClassAndMethod, method display options = None)
    Discovered:  System.Security.Cryptography.X509Certificates.Tests (found 837 of 879 test cases)
    Starting:    System.Security.Cryptography.X509Certificates.Tests (parallel test collections = on, max threads = 8)
      System.Security.Cryptography.X509Certificates.Tests.X509StoreTests.X509Store_MachineStoreLoadSkipsInvalidFiles [SKIP]
        Condition(s) not met: "NotRunningAsRootAndRemoteExecutorSupported"
      System.Security.Cryptography.X509Certificates.Tests.X509FilesystemTests.VerifyCrlCache [SKIP]
        Condition(s) not met: "RunManualTests"
    Finished:    System.Security.Cryptography.X509Certificates.Tests
  === TEST EXECUTION SUMMARY ===
     System.Security.Cryptography.X509Certificates.Tests  Total: 1860, Errors: 0, Failed: 0, Skipped: 2, Time: 110.480s
  /projects/runtime/src/libraries/System.Security.Cryptography.X509Certificates/tests
  ----- end Fri Aug 5 05:29:05 PM UTC 2022 ----- exit code 0 ----------------------------------------------------------
  exit code 0 means Exited Successfully
root [ /projects/runtime/src/libraries/System.Security.Cryptography.X509Certificates/tests ]# cat /etc/os-release
NAME="Common Base Linux Mariner"
VERSION="2.0.20220731"
ID=mariner
VERSION_ID="2.0"
PRETTY_NAME="CBL-Mariner/Linux"
ANSI_COLOR="1;34"
HOME_URL="https://aka.ms/cbl-mariner"
BUG_REPORT_URL="https://aka.ms/cbl-mariner"
SUPPORT_URL="https://aka.ms/cbl-mariner"
bartonjs commented 2 years ago

Actually, while the title never mentioned mono, I see the intro text did... reopening while I figure out how to run under mono.

vcsjones commented 2 years ago

If this no longer repros - great. This is holding consolidating the X.509 tests in to the more general S.S.Cryptography/tests.

bartonjs commented 2 years ago

Verified that it's not crashing on mariner.2, but unclear on how to proceed with removing the ActiveIssue labels see long update at https://github.com/dotnet/runtime/issues/57506#issuecomment-1206738959.