Skip to content

Cryptography.Tests: No PEM encoded data found #117163

New issue
New issue
Closed
Closed
Cryptography.Tests: No PEM encoded data found#117163
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabarea-System.Security
Milestone
10.0.0

Description

@jozkee
jozkee
opened on Jun 30, 2025

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1073221
Build error leg or test failing:

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "No PEM encoded data found. (Parameter 'pemData')",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1073221
Error message validated: [No PEM encoded data found. (Parameter 'pemData')]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 6/30/2025 5:37:27 PM UTC

Report

Build Definition Test Pull Request
1113991 dotnet/runtime WasmTestOnChrome-ST-System.Security.Cryptography.Tests.WorkItemExecution
1113411 dotnet/runtime WasmTestOnChrome-ST-System.Security.Cryptography.Tests.WorkItemExecution
1112651 dotnet/runtime WasmTestOnChrome-ST-System.Security.Cryptography.Tests.WorkItemExecution
1112367 dotnet/runtime WasmTestOnChrome-ST-System.Security.Cryptography.Tests.WorkItemExecution
1112200 dotnet/runtime WasmTestOnChrome-ST-System.Security.Cryptography.Tests.WorkItemExecution
1112098 dotnet/runtime WasmTestOnChrome-ST-System.Security.Cryptography.Tests.WorkItemExecution
1111945 dotnet/runtime WasmTestOnChrome-ST-Microsoft.Bcl.Cryptography.Tests.WorkItemExecution
1111636 dotnet/runtime WasmTestOnChrome-ST-System.Security.Cryptography.Tests.WorkItemExecution
1111091 dotnet/runtime WasmTestOnChrome-ST-System.Security.Cryptography.Tests.WorkItemExecution
1110710 dotnet/runtime WasmTestOnChrome-ST-System.Security.Cryptography.Tests.WorkItemExecution

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 10

Activity

  1. jozkee
    added
    Known Build ErrorUse this to report build issues in the .NET Helix tab
    on Jun 30, 2025
  2. dotnet-policy-service
    added
    untriagedNew issue has not been triaged by the area owner
    on Jun 30, 2025
  3. github-actions
    added
    needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area owners
    on Jun 30, 2025
  4. jozkee
    added
    arch-wasmWebAssembly architecture
    area-System.Security
    and removed
    needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area owners
    on Jun 30, 2025

  5. dotnet-policy-service commented on Jun 30, 2025

    @dotnet-policy-service
    dotnet-policy-serviceBot
    on Jun 30, 2025 – with Dotnet Policy Service
    Contributor

    Tagging subscribers to 'arch-wasm': @lewing
    See info in area-owners.md if you want to be subscribed.

  6. dotnet-policy-service commented on Jun 30, 2025

    @dotnet-policy-service
    dotnet-policy-serviceBot
    on Jun 30, 2025 – with Dotnet Policy Service
    Contributor

    Tagging subscribers to this area: @dotnet/area-system-security, @bartonjs, @vcsjones
    See info in area-owners.md if you want to be subscribed.

  7. jozkee commented on Jun 30, 2025

    @jozkee
    jozkee
    on Jun 30, 2025
    MemberAuthor

    Console log: https://helixr1107v0xd1eu3ibi6ka.blob.core.windows.net/dotnet-runtime-refs-heads-release-100-preview6504d1246db64978ad/WasmTestOnChrome-ST-Microsoft.Bcl.Cryptography.Tests/1/console.6263f5ce.log?helixlogtype=result

    ... Many more above

[00:21:10] info: [FAIL] System.Security.Cryptography.Tests.MLDsaTests.ExportSubjectPublicKeyInfo_CallsExportMLDsaPublicKey(algorithm: MLDsaAlgorithm { Name = "ML-DSA-87", PrivateSeedSizeInBytes = 32, PublicKeySizeInBytes = 2592, SecretKeySizeInBytes = 4896, SignatureSizeInBytes = 4627 })
[00:21:10] info: System.ArgumentException : No PEM encoded data found. (Parameter 'pemData')
[00:21:10] info:    at System.Security.Cryptography.Tests.MLDsaTests.<>c__DisplayClass19_0.<ExportSubjectPublicKeyInfo_CallsExportMLDsaPublicKey>b__0(Func`2 export)
[00:21:10] info:    at System.Object.InvokeStub_MLDsaTests.ExportSubjectPublicKeyInfo_CallsExportMLDsaPublicKey(Object , Span`1 )
[00:21:10] info:    at System.Reflection.MethodBaseInvoker.InvokeWithOneArg(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
[00:21:10] info: Finished:    Microsoft.Bcl.Cryptography.Tests.dll
[00:21:10] info: Stored /root/helix/work/workitem/uploads/xharness-output/testResults.xml results 262163 bytes
[00:21:10] info: Finished uploading 262163 bytes of RESULTXML
[00:21:10] info: Xml file was written to the provided writer.
[00:21:10] info: 
[00:21:10] info: === TEST EXECUTION SUMMARY ===
[00:21:10] info: Tests run: 643 Passed: 577 Inconclusive: 0 Failed: 43 Ignored: 0 Skipped: 23

  8. vcsjones commented on Jun 30, 2025

    @vcsjones
    vcsjones
    on Jun 30, 2025
    Member

    I don't see this failure locally on wasm. I get a green run, in both S.S.C. and M.B.C

    <test name="System.Security.Cryptography.Tests.MLDsaTests.ExportSubjectPublicKeyInfo_CallsExportMLDsaPublicKey(algorithm: ML-DSA-44)" type="System.Security.Cryptography.Tests.MLDsaTests" method="ExportSubjectPublicKeyInfo_CallsExportMLDsaPublicKey" time="0.003125" result="Pass" />
<test name="System.Security.Cryptography.Tests.MLDsaTests.ExportSubjectPublicKeyInfo_CallsExportMLDsaPublicKey(algorithm: ML-DSA-65)" type="System.Security.Cryptography.Tests.MLDsaTests" method="ExportSubjectPublicKeyInfo_CallsExportMLDsaPublicKey" time="0.001556" result="Pass" />
<test name="System.Security.Cryptography.Tests.MLDsaTests.ExportSubjectPublicKeyInfo_CallsExportMLDsaPublicKey(algorithm: ML-DSA-87)" type="System.Security.Cryptography.Tests.MLDsaTests" method="ExportSubjectPublicKeyInfo_CallsExportMLDsaPublicKey" time="0.003191" result="Pass" />

    There are a lot of failures in that run that I can no longer reproduce, either.

    [00:54:15] info: [FAIL] System.Security.Cryptography.Tests.PemEncodingFindTryTests.Find_Success_DecodeSize(base64: "cGU=", expectedSize: 2)
[00:54:15] info: Assert.Equal() Failure: Values differ
[00:54:15] info: Expected: 2
[00:54:15] info: Actual:   3

    I wonder if a more general bug fix / codegen fix was made.

  9. jozkee commented on Jun 30, 2025

    @jozkee
    jozkee
    on Jun 30, 2025
    MemberAuthor

    This is from a preview6 run from Jun 20th, it might have been fixed in main already. Opened it to raise awareness in case it hasn't been fixed.

  10. lewing commented on Jul 1, 2025

    @lewing
    lewing
    on Jul 1, 2025
    Member

    These tests are only running with AOT in runtime-extra-platforms and are also failing in net9 so it probably isn't a new regression.

  11. lewing
    added this to the 10.0.0 milestone on Jul 1, 2025
  12. lewing
    removed
    untriagedNew issue has not been triaged by the area owner
    on Jul 1, 2025

  13. pavelsavara commented on Jul 18, 2025

    @pavelsavara
    pavelsavara
    on Jul 18, 2025
    Member

    speculation: could this be caused by some test file broken/missing on VFS ?

  14. pavelsavara commented on Jul 18, 2025

    @pavelsavara
    pavelsavara
    on Jul 18, 2025
    Member

    Or memory related like #117169

  15. lewing commented on Jul 23, 2025

    @lewing
    lewing
    on Jul 23, 2025
    Member

    or #117665

  16. lewing
    removed
    arch-wasmWebAssembly architecture
    on Jul 23, 2025

  17. lewing commented on Jul 23, 2025

    @lewing
    lewing
    on Jul 23, 2025
    Member

    Updated the title and label to point out this isn't only happening on wasm
    cc @jeffhandley

  18. lewing
    changed the title [-]WasmTestOnChrome-ST-Microsoft.Bcl.Cryptography.Tests: No PEM encoded data found[/-] [+]Cryptography.Tests: No PEM encoded data found[/+] on Jul 23, 2025

  19. jeffhandley commented on Aug 30, 2025

    @jeffhandley
    jeffhandley
    on Aug 30, 2025
    Member

    This was fixed by #118154

  20. jeffhandley
    closed this as completedon Aug 30, 2025
  21. github-actions
    locked and limited conversation to collaborators on Sep 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Known Build ErrorUse this to report build issues in the .NET Helix tabarea-System.Security

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions