Skip to content

System.CodeDom.Compiler.Tests.CodeCompilerTests.GetResponseFileCmdArgs_ValidCmdArgs_ReturnsExpected test failing in CI #34112

Closed

Description

@jozkee

Found on #33459

Error and stack trace:

System.IO.DirectoryNotFoundException : Could not find a part of the path 'C:\Users\runner\AppData\Local\Temp\0lw3mff1\0lw3mff1.cmdline'.
Stack Trace:
    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
    at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
    at System.CodeDom.Compiler.CodeCompiler.GetResponseFileCmdArgs(CompilerParameters options, String cmdArgs)
    /_/src/libraries/System.CodeDom/tests/System/CodeDom/Compiler/CodeCompilerTests.cs(465,0): at System.CodeDom.Compiler.Tests.CodeCompilerTests.GetResponseFileCmdArgs_ValidCmdArgs_ReturnsExpected(String cmdArgs)AAAAAAA

@buyaa-n @krwq

Activity

  1. danmoseley commented on Mar 26, 2020

    @danmoseley
    Contributor

    @jozkee its worth mentioning this was not on .NET Core: net472-Windows_NT-Release-x86-Windows.10.Amd64.Client19H1.Open

    either the path was never created correctly, or it got deleted async. this test has its own TempFileCollection. my guess is the bug is in the product - in creating a unique file, or verifying it's created successfully. the code for both is different to .NET Core. it's not obvious to me what the issue could be in briefly looking.

    probably most reasonable to just disable CodeDom tests from running on .NET Framework anymore.

  2. krwq commented on Apr 21, 2020

    @krwq
    Member

    @jozkee have you seen any CodeDom tests failing recently with similar stack trace? Did it pass after retrying? Have you seen it failing anywhere on .NET Core? Full framework is very unlikely to get patched at this point even if we find a fix.

  3. v-haren commented on May 6, 2020

    @v-haren

    failed again in job: runtime 20200505.59

    failed test: System.CodeDom.Compiler.Tests.CodeCompilerTests.GetResponseFileCmdArgs_ValidCmdArgs_ReturnsExpected(cmdArgs: null)

    Error message

    System.IO.DirectoryNotFoundException : Could not find a part of the path 'C:\Users\runner\AppData\Local\Temp\pnfz2ogr\pnfz2ogr.cmdline'.
    
    
    Stack trace
       at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
       at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
       at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
       at System.CodeDom.Compiler.CodeCompiler.GetResponseFileCmdArgs(CompilerParameters options, String cmdArgs)
       at System.CodeDom.Compiler.Tests.CodeCompilerTests.GetResponseFileCmdArgs_ValidCmdArgs_ReturnsExpected(String cmdArgs) in /_/src/libraries/System.CodeDom/tests/System/CodeDom/Compiler/CodeCompilerTests.cs:line 465
    
  4. buyaa-n commented on Jun 22, 2020

    @buyaa-n
    Contributor

    As Dan mentioned sounds better to disable the tests on .NET Framework

  5. removed
    untriagedNew issue has not been triaged by the area owner
    on Jun 22, 2020
  6. added this to the 5.0.0 milestone on Jun 22, 2020
  7. added
    help wanted[up-for-grabs] Good issue for external contributors
    on Jun 22, 2020
  8. modified the milestones: 5.0.0, 6.0.0 on Jun 22, 2020
  9. buyaa-n commented on Feb 16, 2021

    @buyaa-n
    Contributor

    The failure logs are gone, from the stack trace and log, and after looking into the code in .NET Framework i don't think this issue is caused by a code/test bug, by accounting that this failure hasn't happened for a while i am gonna just close this issue

  10. ghost locked as resolved and limited conversation to collaborators on Mar 18, 2021
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

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions