Skip to content

Interop\StringMarshalling\UTF8\UTF8Test failing in outerloop #69349

Closed

Description

@jakobbotsch

Pipeline run: https://dev.azure.com/dnceng/public/_build/results?buildId=1771054
Example failure:

  Starting:    Interop.StringMarshalling.XUnitWrapper (parallel test collections = on, max threads = 2)
    Interop/StringMarshalling/UTF8/UTF8Test/UTF8Test.sh [FAIL]
      free(): invalid pointer
      /datadisks/disk1/work/B90F09CF/w/B12609F6/e/Interop/StringMarshalling/UTF8/UTF8Test/UTF8Test.sh: line 382:  8806 Aborted                 (core dumped) $LAUNCHER $ExePath "${CLRTestExecutionArguments[@]}"
      
      Return code:      1
      Raw output file:      /datadisks/disk1/work/B90F09CF/w/B12609F6/uploads/Reports/Interop.StringMarshalling/UTF8/UTF8Test/UTF8Test.output.txt
      Raw output:
      BEGIN EXECUTION
      /datadisks/disk1/work/B90F09CF/p/corerun -p System.Reflection.Metadata.MetadataUpdater.IsSupported=false UTF8Test.dll ''
      [createdump] Gathering state for process 8806 corerun
      [createdump] Crashing thread 00002266 signal 00000006
      [createdump] Writing minidump with heap to file /home/helixbot/dotnetbuild/dumps/coredump.8806.dmp
      [createdump] Written 129400832 bytes (31592 pages) to core file
      [createdump] Dump successfully written
      Expected: 100
      Actual: 134
      END EXECUTION - FAILED
      Test Harness Exitcode is : 1
      To run the test:
      > set CORE_ROOT=/datadisks/disk1/work/B90F09CF/p
      > /datadisks/disk1/work/B90F09CF/w/B12609F6/e/Interop/StringMarshalling/UTF8/UTF8Test/UTF8Test.sh
      Expected: True
      Actual:   False
      Stack Trace:
           at Interop_StringMarshalling._UTF8_UTF8Test_UTF8Test_._UTF8_UTF8Test_UTF8Test_sh()

Activity

  1. ghost added
    untriagedNew issue has not been triaged by the area owner
    on May 14, 2022
  2. added this to the 7.0.0 milestone on May 14, 2022
  3. ghost removed
    untriagedNew issue has not been triaged by the area owner
    on May 14, 2022
  4. AaronRobinsonMSFT commented on May 14, 2022

    @AaronRobinsonMSFT
    Member

    @jkotas Seems like #69043 might have caused a regression.

  5. jkotas commented on May 14, 2022

    @jkotas
    Member

    I will take a look

  6. added a commit that references this issue on May 14, 2022
    6951661
  7. ghost added
    in-prThere is an active PR which will close this issue when it is merged
    on May 14, 2022
  8. added a commit that references this issue on May 15, 2022
    e22c63e
  9. ghost removed
    in-prThere is an active PR which will close this issue when it is merged
    on May 15, 2022
  10. ghost locked as resolved and limited conversation to collaborators on Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions