[ci-scan] Test failure: OpenSslErrorTests.GetSslLibraryReason_UsesLayoutOfLoadedOpenSsl on tvOS
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 22/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Stack tecnológico
- csharp
- Área
- cryptography, testing-qa
Línea de trabajo
Start with the failing test OpenSslErrorTests.GetSslLibraryReason_UsesLayoutOfLoadedOpenSsl in System.Net.Security.Unit.Tests and the DllNotFoundException for libSystem.Security.Cryptography.Native.OpenSsl thrown from the Interop.OpenSsl static constructor on tvOS. The issue does not say what to change, so first confirm with the maintainers where the tvOS native library is expected to be packaged or loaded. Done means the test passes on tvos-arm64 in both CoreCLR and NativeAOT legs.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1659071
Build error leg or test failing: tvos-arm64 Release AllSubsets_CoreCLR-System.Net.Security.Unit.Tests / System.Net.Security.Tests.OpenSslErrorTests.GetSslLibraryReason_UsesLayoutOfLoadedOpenSsl
Also affected: tvos-arm64 Release AllSubsets_NativeAOT.
Pipeline: runtime-extra-platforms, definition 154, main.
First build it occurred: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1648254 (finished 2026-10-25; earliest verified occurrence in the ten-build sample, not the established introduction).
Follow-up build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1661087 (finished 2026-11-03), same missing-library failure on both runtime variants.
KBE authoring guidance (ci-failure-scan)
Error Detailsis for readers. Paste the full exception, stack trace, or build error excerpt so the failure is understandable without opening the raw log.- Build Analysis parses only the single JSON block under
Error Message. ErrorMessageis a case-sensitive ordinalString.Containssubstring copied verbatim from the failing log.- Set
BuildRetrytotrueonly for a clear infrastructure retry case.ExcludeConsoleLogdisables Helix console-log scanning.
Error Details
All nine theory cases attempt to initialize the OpenSSL interop library on tvOS and fail because libSystem.Security.Cryptography.Native.OpenSsl cannot be loaded. Source CoreCLR results: 136 tests, 124 passed, 9 failed, 3 ignored. The NativeAOT work item has the same missing-library exception. This scan does not establish the underlying product or test-configuration fix.
The same exception was verified in seven distinct source-and-prior builds among ten sampled: 1648254, 1648681, 1653767, 1655451, 1657310, 1658360, and 1659071. Builds without this failed work item's console do not establish that the test passed. The true origin may predate 2026-10-25.
Log prefixes and repeated application-bundle library-search paths are omitted below; the complete exception chain and stack frames are retained:
[FAIL] System.Net.Security.Tests.OpenSslErrorTests.GetSslLibraryReason_UsesLayoutOfLoadedOpenSsl(error: 338067735, isOpenSsl3: False, expected: 279)
System.TypeInitializationException : The type initializer for 'OpenSsl' threw an exception.
---- System.TypeInitializationException : The type initializer for 'CryptoInitializer' threw an exception.
-------- System.DllNotFoundException : Unable to load shared library 'libSystem.Security.Cryptography.Native.OpenSsl' or one of its dependencies. In order to help diagnose loading problems, consider setting the DYLD_PRINT_LIBRARIES environment variable:
at Interop.OpenSsl.GetSslLibraryReason(UInt32 error, Boolean isOpenSsl3)
at System.Net.Security.Tests.OpenSslErrorTests.GetSslLibraryReason_UsesLayoutOfLoadedOpenSsl(UInt32 error, Boolean isOpenSsl3, Int32 expected)
at InvokeStub_OpenSslErrorTests.GetSslLibraryReason_UsesLayoutOfLoadedOpenSsl(Object, Object, IntPtr*)
at System.Reflection.IntrinsicInvokeHelper.Invoke(InvokeState& state, InvokerStrategy& strategy, InvokeFunc_RefArgs& invokeFunc, MethodBase method, RuntimeType[] argumentTypes, Object obj, IntPtr* args, Boolean backwardsCompat)
at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span`1 copyOfArgs, BindingFlags invokeAttr)
----- Inner Stack Trace -----
at Interop.OpenSsl..cctor()
at System.Runtime.CompilerServices.InitHelpers.CallClassConstructor(Void* cctor, Void* instantiatingArg, Exception* pException)
----- Inner Stack Trace -----
at Interop.CryptoInitializer..cctor()
at System.Runtime.CompilerServices.InitHelpers.CallClassConstructor(Void* cctor, Void* instantiatingArg, Exception* pException)
Error Message
{
"ErrorMessage": [
"[FAIL] System.Net.Security.Tests.OpenSslErrorTests.GetSslLibraryReason_UsesLayoutOfLoadedOpenSsl",
"System.DllNotFoundException : Unable to load shared library 'libSystem.Security.Cryptography.Native.OpenSsl' or one of its dependencies."
],
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
Agentic workflow metadata (ci-failure-scan)
Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 18 hits in failure.log
Both elements occur in order in the failing test output and each has 18 literal matches in the saved source console. The failure marker does not match passing or skipped output.
Filed by ci-failure-scan (detection only). ci-failure-fix walks open [ci-scan] KBEs and either opens a small fix PR or comments here to loop in owners — it never disables the test.
[!NOTE]
Generated by GitHub Copilot.
Generated by CI Outer-Loop Failure Scanner · copilot · gpt61 · ~235 AIC · ⌖ ~13 AIC · ⊞ 33.3K · ◷
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 5 | 5 |
- Lenguaje dominante
- C#
- Estrellas
- 18.4k
- Forks
- 5.8k
- Merge medio
- 2 d 12 h
- PR fusionados (30 d)
- 581
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de dotnet/runtime
-
area-System.Collections untriaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
dotnet/runtime#137167 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Incorrect loop bound in SizeOptIListSelectIterator.ToListPosiblemente ocupada @equmagg la tomó hace 2 días. Abiertoarea-System.Collections untriaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
dotnet/runtime#137126 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
DbTransaction.SupportsSavepoints docs say Release/ReleaseAsync are expected to throw, but they are no-ops by designPosiblemente ocupada @alaricd la tomó hace 3 días. Abiertoarea-System.Transactions untriaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
dotnet/runtime#137040 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
FileSystemGlobbing: Matcher throws ArgumentOutOfRangeException when the rootDir is the same value as the filePosiblemente ocupada @makazeu la tomó hace 4 días. Abiertoarea-Extensions-FileSystem
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
dotnet/runtime#136989 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Configuration binder source generator emits unqualified List<T> when binding arrays without implicit usingsPosiblemente ocupada @makazeu la tomó hace 4 días. Abiertoarea-Extensions-Configuration bug source-generator
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
dotnet/runtime#136972 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de dotnet/runtime
Issues similares
-
Assert.That on a null non-generic IEnumerable throws ArgumentNullException, so IsNull() cannot passAbiertobug P2
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
area/automation area/sdk kind/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
unoplatform/uno.templates#2406 ·
Los mantenedores suelen responder en 1 día
-
bug frontend ui
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
documentation trivial
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día