Skip to content

[mono][ios] System.Formats.Tar.Tests are failing with System.ArgumentException #88049

Closed

Description

@kotlarmilos

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=320749&view=results
Build error leg or test failing: iossimulator-x64 Release AllSubsets_Mono
Pull request: #88042

Error Message

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

{
  "ErrorMessage": "System.ArgumentException : The field 'Name' exceeds the maximum allowed length for this format",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=320749
Result validation: ✅ Known issue matched with the provided build.

Report

Build Definition Test Pull Request
495924 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
492182 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution #95757
491743 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution #95733
489669 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
484466 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
478851 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
478790 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
478779 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
477633 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
477305 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
476004 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
473580 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
473434 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
473400 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
472901 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
472857 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
471800 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
471653 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
471584 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
471393 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
470325 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
468967 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
468844 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
468590 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution
468095 dotnet/runtime System.Formats.Tar.Tests.WorkItemExecution

Summary

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

Activity

  1. added this to the 8.0.0 milestone on Jun 26, 2023
  2. kotlarmilos commented on Jul 11, 2023

    @kotlarmilos
    MemberAuthor

    @carlossanlop It seems that the regression was introduced in #87534. The issue appears to be specific to the ios and tvos simulators.

  3. self-assigned this
    on Jul 13, 2023
  4. kotlarmilos commented on Jul 24, 2023

    @kotlarmilos
    MemberAuthor

    This fails only on apple mobile simulators that run Mono Interpreter. My assumption is that the GetUtf8TextLength doesn't return the same value with Interpreter and AOT, but still have to confirm that locally.

    /cc: @BrzVlad

    const ushort limit = 100;
    ReadOnlySpan<char> name = _name;
    int encodedLength = GetUtf8TextLength(name);
    
    if (encodedLength > FieldLengths.Name)
    {
        if (_format is TarEntryFormat.V7)
        {
            throw new ArgumentException(SR.Format(SR.TarEntryFieldExceedsMaxLength, nameof(TarEntry.Name)), ArgNameEntry);
        }
    
        int utf16NameTruncatedLength = GetUtf16TruncatedTextLength(name, FieldLengths.Name);
        name = name.Slice(0, utf16NameTruncatedLength);
    }
  5. kotlarmilos commented on Jul 31, 2023

    @kotlarmilos
    MemberAuthor

    This issue is also occurring on iOS/tvOS devices. For instance in: https://dev.azure.com/dnceng-public/public/_build/results?buildId=357141&view=results. The length of fields exceeds the values set in:

    @carlossanlop Should we update the fields length to match the following examples?

    public static IEnumerable<object[]> GetExactRootDirMatchCases()

  6. carlossanlop commented on Aug 8, 2023

    @carlossanlop
    Contributor

    Hi - The Path length used for V7 should stay as is, it's what the spec indicates and it should be respected.

    The test could be modified so that the temporary path directory is created with a much shorter path. Would that work?

  7. steveisok commented on Aug 8, 2023

    @steveisok
    Member

    Hi - The Path length used for V7 should stay as is, it's what the spec indicates and it should be respected.

    The test could be modified so that the temporary path directory is created with a much shorter path. Would that work?

    Yes, definitely.

  8. 3 remaining items

  9. removed this from the 9.0.0 milestone on Nov 15, 2023
  10. ghost added
    untriagedNew issue has not been triaged by the area owner
    on Nov 15, 2023
  11. added this to the 9.0.0 milestone on Dec 6, 2023
  12. ghost removed
    untriagedNew issue has not been triaged by the area owner
    on Dec 6, 2023
  13. carlossanlop commented on Dec 6, 2023

    @carlossanlop
    Contributor

    @kotlarmilos @steveisok the folder used to store files needs to have a shorter path for the test to work (the failure is expected for this tar format). Can you please change it to a shorter directory for this platform?

  14. self-assigned this
    on Dec 6, 2023
  15. ghost added
    in-prThere is an active PR which will close this issue when it is merged
    on Dec 7, 2023
  16. ghost removed
    in-prThere is an active PR which will close this issue when it is merged
    on Dec 11, 2023
  17. ghost added
    in-prThere is an active PR which will close this issue when it is merged
    on Dec 11, 2023
  18. ghost removed
    in-prThere is an active PR which will close this issue when it is merged
    on Dec 11, 2023
  19. ghost added
    in-prThere is an active PR which will close this issue when it is merged
    on Dec 11, 2023
  20. ghost removed
    in-prThere is an active PR which will close this issue when it is merged
    on Dec 11, 2023
  21. locked and limited conversation to collaborators on Jan 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions