You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
System.CodeDom.Compiler.Tests.CodeCompilerTests.GetResponseFileCmdArgs_ValidCmdArgs_ReturnsExpected test failing in CI #34112
@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.
@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.
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
Activity
danmoseley commentedon Mar 26, 2020
@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.
danmoseley commentedon Mar 26, 2020
possibly relevant but not clear how
https://github.com/dotnet/corefx/pull/12680/files#diff-7344081853370a2ec275db83f03f7076
https://referencesource.microsoft.com/#System/compmod/system/codedom/compiler/TempFiles.cs,227
krwq commentedon Apr 21, 2020
@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.
v-haren commentedon May 6, 2020
failed again in job: runtime 20200505.59
failed test: System.CodeDom.Compiler.Tests.CodeCompilerTests.GetResponseFileCmdArgs_ValidCmdArgs_ReturnsExpected(cmdArgs: null)
Error message
buyaa-n commentedon Jun 22, 2020
As Dan mentioned sounds better to disable the tests on .NET Framework
buyaa-n commentedon Feb 16, 2021
The failure logs are gone, from the stack trace and log, and after looking into the code in
.NET Frameworki 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