runtime: System.Security.Cryptography.OpenSsl.Tests failing on CI runs

Tests are crashing on several OSX runs

===========================================================================================================
/private/tmp/helix/working/BB380A7A/w/CADB0A98/e /private/tmp/helix/working/BB380A7A/w/CADB0A98/e
  Discovering: System.Security.Cryptography.OpenSsl.Tests (method display = ClassAndMethod, method display options = None)
No usable version of libssl was found
./RunTests.sh: line 161: 65451 Abort trap: 6           "$RUNTIME_PATH/dotnet" exec --runtimeconfig System.Security.Cryptography.OpenSsl.Tests.runtimeconfig.json --depsfile System.Security.Cryptography.OpenSsl.Tests.deps.json xunit.console.dll System.Security.Cryptography.OpenSsl.Tests.dll -xml testResults.xml -nologo -nocolor -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing -notrait category=nonnetcoreapptests -notrait category=nonosxtests $RSP_FILE
/private/tmp/helix/working/BB380A7A/w/CADB0A98/e
----- end Thu Jan 23 05:44:06 PST 2020 ----- 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.

Builds

Test Runs

netcoreapp5.0-OSX-Release-x64-CoreCLR_release-OSX.1013.Amd64.Open
netcoreapp5.0-OSX-Release-x64-CoreCLR_release-OSX.1014.Amd64.Open
netcoreapp5.0-OSX-Release-x64-Mono_release-OSX.1014.Amd64.Open

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 32 (21 by maintainers)

Most upvoted comments

Apologies for the delay in getting this resolved, we had some miscommunication on our side and we are going through the rest of the machines to fix them. ETA is tomorrow morning.

JpratherMS on Feb 6, 2020

Think at this point we need to pull those configurations until we can get the underlying issue fixed.

I was already working on that, talked with @JpratherMS offline and he hopes the work to update the machines will be done by EOD. He will update if so, if it is not ready I’ll put up my PR to disable the affected tests on OSX.

safern on Feb 6, 2020

Yes it is the same error, mono just crashes in a different way and prints the whole call stack, but it is caused by the same: No usable version of libssl was found.

Thanks @ahsonkhan

safern on Feb 5, 2020

Data from the last 100 builds (CI and PR)

Builds

Build	Pull Request	Test Failure Count
#507937	#1787	10
#507961	#31734	1
#508096	Rolling	1
#508266	#2087	1
#508472	#2275	1
#508547	#31765	1
#508623	#31807	1
#508780	#31765	1
#508787	#27540	1
#508835	#5523	1
#508862	#2140	1
#508923	#31819	1
#509133	#31826	1
#509169	#31802	1
#509342	#1612	20
#509347	#2259	1
#509362	Rolling	1
#509423	#1787	5
#509654	#31838	5
#509747	Rolling	1
#510085	#31854	1
#510294	#31814	1

Configurations

netcoreapp5.0-OSX-Debug-x64-CoreCLR_checked-OSX.1013.Amd64.Open
netcoreapp5.0-OSX-Debug-x64-CoreCLR_release-OSX.1013.Amd64.Open
netcoreapp5.0-OSX-Debug-x64-CoreCLR_release-OSX.1014.Amd64.Open
netcoreapp5.0-OSX-Debug-x64-Mono_release-OSX.1013.Amd64.Open
netcoreapp5.0-OSX-Debug-x64-Mono_release-OSX.1014.Amd64.Open
netcoreapp5.0-OSX-Release-x64-Mono_release-OSX.1014.Amd64.Open

Helix Logs

Build	Pull Request	Console	Core
#507937	#1787	console.338b1956.log
#507937	#1787	console.b76cc7b6.log
#507937	#1787	console.55abdc57.log
#507937	#1787	console.46da5f7c.log
#507937	#1787	console.df261f95.log
#507937	#1787	console.8558d07e.log
#507937	#1787	console.b5f5c68c.log
#507937	#1787	console.aba60104.log
#507937	#1787	console.86a05f30.log
#507937	#1787	console.13060cb7.log
#507961	#31734	console.075b1564.log	core.31566
#508096	Rolling	console.6d912e31.log	core.37103
#508266	#2087	console.79f77369.log	core.42773
#508472	#2275	console.ceed47a0.log	core.44769
#508547	#31765	console.8a957c50.log	core.47155
#508623	#31807	console.f30e2088.log	core.48721
#508780	#31765	console.0b771628.log	core.4026
#508787	#27540	console.8d8e1010.log	core.4686
#508835	#5523	console.9a2025a2.log	core.5188
#508862	#2140	console.dc340c3f.log	core.5999
#508923	#31819	console.923c5d72.log	core.7127
#509133	#31826	console.185f15e8.log	core.9506
#509169	#31802	console.3ed533eb.log	core.11807
#509342	#1612	console.e7f10be1.log	core.1000.22
#509342	#1612	console.0683c3ae.log	core.1000.57
#509342	#1612	console.6f815067.log	core.1000.5878
#509342	#1612	console.9dee786b.log	core.1000.6159
#509342	#1612	console.399a5c79.log	core.1000.7512
#509342	#1612	console.17059d0d.log	core.1000.11287
#509342	#1612	console.140aba91.log	core.1000.7884
#509342	#1612	console.905f82c4.log
#509342	#1612	console.781e76fc.log
#509342	#1612	console.2ded3daa.log
#509342	#1612	console.329188b9.log
#509342	#1612	console.50d9e385.log
#509342	#1612	console.fd7064ef.log
#509342	#1612	console.265efa80.log
#509342	#1612	console.660f0d2f.log
#509342	#1612	console.cc8940d2.log	core.50894
#509342	#1612	console.7fa942a1.log	core.17123
#509342	#1612	console.0d7eed7c.log
#509342	#1612	console.4fcd040b.log
#509342	#1612	console.0b7b0aef.log
#509347	#2259	console.886e5091.log	core.14348
#509362	Rolling	console.0584d0a8.log	core.12129
#509423	#1787	console.1eb1dc5f.log
#509423	#1787	console.dc372806.log
#509423	#1787	console.b32d0cb4.log
#509423	#1787	console.11f19c52.log
#509423	#1787	console.53b4997f.log
#509654	#31838	console.82475420.log
#509654	#31838	console.5f2b49ac.log
#509654	#31838	console.0edaed0e.log
#509654	#31838	console.6469a128.log
#509654	#31838	console.c328dcce.log
#509747	Rolling	console.749984ce.log	core.20578
#510085	#31854	console.e56c99e9.log	core.26802
#510294	#31814	console.b5a100a6.log	core.27087

jaredpar on Feb 6, 2020

Thanks for reaching out, we found an issue with our process in discovering the ones that are not configured correctly. We are working on resolving that now, I will update again when that is completed.

JpratherMS on Feb 4, 2020