Skip to content

[mono] Apple mobile runtime tests can't load BigArray_32_1 in ClassLoader tests, the size is too big. #106797

Closed

Description

@matouskozak

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=784159
Build error leg or test failing: Loader_classloader
Affected CI: [tvos,ios]_arm64_release_allsubsets_mono_runtimetests (runtime-extra-platforms)
Range of commits: 779baa6...631778a

Stack trace:

[19:39:55.4517280] 2024-08-21 16:39:55.525 Loader_classloader[84744:102779304] System.TypeLoadException: Can't load type BigArray_32_1. The size is too big.
[19:39:55.4517630]    at __GeneratedMainWrapper.Main()

Error Message

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

{
  "ErrorPattern": "Detected exit code 101 from \\/tmp\\/helix\\/working\\/.*\\/uploads\\/net\\.dot\\.Loader_classloader\\.log",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=784159
Error message validated: [Detected exit code 101 from \/tmp\/helix\/working\/.*\/uploads\/net\.dot\.Loader_classloader\.log]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 8/22/2024 7:07:41 AM UTC

Report

Summary

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

Activity

  1. added
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    untriagedNew issue has not been triaged by the area owner
    Known Build ErrorUse this to report build issues in the .NET Helix tab
    on Aug 22, 2024
  2. dotnet-policy-service commented on Aug 22, 2024

    @dotnet-policy-service
    Contributor

    Tagging subscribers to 'os-ios': @vitek-karas, @kotlarmilos, @ivanpovazan, @steveisok, @akoeplinger
    See info in area-owners.md if you want to be subscribed.

  3. dotnet-policy-service commented on Aug 22, 2024

    @dotnet-policy-service
    Contributor

    Tagging subscribers to 'os-tvos': @vitek-karas, @kotlarmilos, @ivanpovazan, @steveisok, @akoeplinger
    See info in area-owners.md if you want to be subscribed.

  4. matouskozak commented on Aug 22, 2024

    @matouskozak
    MemberAuthor

    Likely introduced by the new tests in #104393 @steveisok, @lambdageek

  5. added this to the 10.0.0 milestone on Aug 22, 2024
  6. removed
    untriagedNew issue has not been triaged by the area owner
    on Aug 22, 2024
  7. lambdageek commented on Aug 22, 2024

    @lambdageek
    Member

    We should probably ifdef the 32-bit/64-bit structs in that test

  8. matouskozak commented on Nov 5, 2024

    @matouskozak
    MemberAuthor

    We should probably ifdef the 32-bit/64-bit structs in that test

    There is something off with the current Mono support. I tried removing completely the 32-bit code and it failed on Assert.Throws<TypeLoadException>(() => sizeof(BigArray_64_2));

    Xunit.Sdk.ThrowsException: Assert.Throws() Failure: No exception was thrown
    Expected: typeof(System.TypeLoadException)
       at Xunit.Assert.Throws(Type exceptionType, Exception exception) in /_/src/Microsoft.DotNet.XUnitAssert/src/ExceptionAsserts.cs:line 47
       at Xunit.Assert.Throws[TypeLoadException](Func`1 testCode) in /_/src/Microsoft.DotNet.XUnitAssert/src/ExceptionAsserts.cs:line 113
       at LargeStructSize.TestLargeStructSize() in <PATH>/src/tests/Loader/classloader/SequentialLayout/ManagedSequential/LargeStructSize_Mono.cs:line 48
    
  9. locked and limited conversation to collaborators on Dec 26, 2024
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

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions