Test failure : Interop\\PInvoke\\Vector2_3_4\\Vector2_3_4\\Vector2_3_4.cmd #47259

Activity

1. VincentBu

   added

   arch-x86

   os-windows

   JitStressCLR JIT issues involving JIT internal stress modesCLR JIT issues involving JIT internal stress modes

   on Jan 21, 2021
2. ghost added

   area-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMICLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI

   on Jan 21, 2021
3. ghost added

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Jan 21, 2021
4. jkoritzinsky commented on Jan 21, 2021

   

   jkoritzinsky

   on Jan 21, 2021

   Member

   More actions

   @sandreenko my guess is this is related to the x86 simd8 support.
5. BruceForstall

   added this to the 6.0.0 milestone on Jan 21, 2021
6. BruceForstall

   removed

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Jan 21, 2021
7. BruceForstall

   assigned

   sandreenko

   on Jan 21, 2021
8. VincentBu commented on Feb 1, 2021

   

   VincentBu

   on Feb 1, 2021

   ContributorAuthor

   More actions

   Failed again in runtime-coreclr jitstressregs 20210131.1

   Failed tests:

   CoreCLR windows x86 Checked jitstressregs0x80 @ Windows.10.Amd64.Open
           - Interop\\PInvoke\\Vector2_3_4\\Vector2_3_4\\Vector2_3_4.cmd
   

   Error message:

   Return code:      1
   Raw output file:      C:\h\w\B19A0942\w\B1E3097F\e\Interop\PInvoke\Reports\Interop.PInvoke\Vector2_3_4\Vector2_3_4\Vector2_3_4.output.txt
   Raw output:
   BEGIN EXECUTION
    "C:\h\w\B19A0942\p\corerun.exe" Vector2_3_4.dll 
   Running RunVector2Tests... 
   TestLibrary.AssertTestException: Assert.AreEqual: Expected: [<71, 999>]. Actual: [<0, 999>]. 
      at TestLibrary.Assert.HandleFail(String assertionName, String message)
      at TestLibrary.Assert.AreEqual[T](T expected, T actual, String message)
      at Vector2_3_4Test.RunVector2Tests()
      at Vector2_3_4Test.Main()
   Expected: 100
   Actual: 101
   END EXECUTION - FAILED
   FAILED
   Test Harness Exitcode is : 1
   To run the test:
   > set CORE_ROOT=C:\h\w\B19A0942\p
   > C:\h\w\B19A0942\w\B1E3097F\e\Interop\PInvoke\Vector2_3_4\Vector2_3_4\Vector2_3_4.cmd
   
   stack trace:
      at Interop_PInvoke._Vector2_3_4_Vector2_3_4_Vector2_3_4_._Vector2_3_4_Vector2_3_4_Vector2_3_4_cmd()
   
9. ghost added

   in-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged

   on Feb 6, 2021
10. VincentBu commented on Feb 8, 2021

    

    VincentBu

    on Feb 8, 2021

    ContributorAuthor

    More actions

    Failed again in runtime-coreclr jitstressregs 20210207.1

    Failed test:

    CoreCLR windows x86 Checked jitstressregs0x80 @ Windows.10.Amd64.Open
    
       -Interop\\PInvoke\\Vector2_3_4\\Vector2_3_4\\Vector2_3_4.cmd
    

    Error message:

    Return code: 1
    Raw output file: C:\h\w\A63C08EF\w\B86909D1\e\Interop\PInvoke\Reports\Interop.PInvoke\Vector2_3_4\Vector2_3_4\Vector2_3_4.output.txt
    Raw output:
    BEGIN EXECUTION
     "C:\h\w\A63C08EF\p\corerun.exe" Vector2_3_4.dll 
    Running RunVector2Tests... 
    TestLibrary.AssertTestException: Assert.AreEqual: Expected: [<71, 999>]. Actual: [<0, 999>]. 
     at TestLibrary.Assert.HandleFail(String assertionName, String message)
     at TestLibrary.Assert.AreEqual[T](T expected, T actual, String message)
     at Vector2_3_4Test.RunVector2Tests()
     at Vector2_3_4Test.Main()
    Expected: 100
    Actual: 101
    END EXECUTION - FAILED
    FAILED
    Test Harness Exitcode is : 1
    To run the test:
    > set CORE_ROOT=C:\h\w\A63C08EF\p
    > C:\h\w\A63C08EF\w\B86909D1\e\Interop\PInvoke\Vector2_3_4\Vector2_3_4\Vector2_3_4.cmd
    Expected: True
    Actual: False
    
    Stack trace
       at Interop_PInvoke._Vector2_3_4_Vector2_3_4_Vector2_3_4_._Vector2_3_4_Vector2_3_4_Vector2_3_4_cmd()
    
    
11. sandreenko

    closed this as completedin #47843on Feb 9, 2021
12. ghost removed

    in-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged

    on Feb 9, 2021
13. ghost locked as resolved and limited conversation to collaborators on Mar 11, 2021