Repository navigation
Can_Run_App_With_StatiHost installer test failure in CI #42101
Description
Activity
- addeduntriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner
on Sep 11, 2020 - addedtest-bugProblem in test source code (most likely)Problem in test source code (most likely)and removeduntriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner
on Sep 14, 2020 - addedblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
on Oct 14, 2020 I have what may be the same issue, with an extra clue - @vitek-karas does this help?
System.ComponentModel.Win32Exception : Text file busy Stack trace at System.Diagnostics.Process.ForkAndExecProcess(String filename, String[] argv, String[] envp, String cwd, Boolean redirectStdin, Boolean redirectStdout, Boolean redirectStderr, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec) at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo) at System.Diagnostics.Process.Start() at Microsoft.DotNet.Cli.Build.Framework.Command.Start() in /_/src/installer/tests/TestUtils/Command.cs:line 199 at Microsoft.DotNet.Cli.Build.Framework.Command.Execute(Boolean fExpectedToFail) in /_/src/installer/tests/TestUtils/Command.cs:line 239 at Microsoft.DotNet.Cli.Build.Framework.Command.Execute() in /_/src/installer/tests/TestUtils/Command.cs:line 171 at AppHost.Bundle.Tests.StaticHost.Can_Run_App_With_StatiHost() in /_/src/installer/tests/Microsoft.NET.HostModel.Tests/AppHost.Bundle.Tests/StaticHost.cs:line 27This is in 5.0 branch
https://dev.azure.com/dnceng/public/_build/results?buildId=852073&view=ms.vss-test-web.build-test-results-tab&runId=27196228&paneView=debug&resultId=100011@jaredpar if this is rare, but did break a CI job, is it appropriate to set 'blocking-clean-ci' or is that just for more common issues? Also, how to notify runfo about it so that it autolinks when it happens again?
Also note this was Installer-coreclr-Linux_musl_x64-Release
This message apparently means that we are trying to execute an executable while it is being modified - apparently in its text section.
This is failing about once a day right now so blocking clean CI is appropriate here.
1 remaining item
@agocke could someone maybe take a look?
failed again in job: runtime 20201217.40
failed test: Can_Run_App_With_StatiHost
Installer-coreclr-Linux_x64-Release
Error message
System.ComponentModel.Win32Exception : Text file busy Stack trace at System.Diagnostics.Process.ForkAndExecProcess(String filename, String[] argv, String[] envp, String cwd, Boolean redirectStdin, Boolean redirectStdout, Boolean redirectStderr, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec) at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo) at System.Diagnostics.Process.Start() at Microsoft.DotNet.Cli.Build.Framework.Command.Start() in /_/src/installer/tests/TestUtils/Command.cs:line 199 at Microsoft.DotNet.Cli.Build.Framework.Command.Execute(Boolean fExpectedToFail) in /_/src/installer/tests/TestUtils/Command.cs:line 239 at Microsoft.DotNet.Cli.Build.Framework.Command.Execute() in /_/src/installer/tests/TestUtils/Command.cs:line 171 at AppHost.Bundle.Tests.StaticHost.Can_Run_App_With_StatiHost() in /_/src/installer/tests/Microsoft.NET.HostModel.Tests/AppHost.Bundle.Tests/StaticHost.cs:line 27Removing blocking tag due to low incidence
cc: @agocke
- removedblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
on Mar 15, 2021 Failed again in runtime 20210601.76
Failed test:
Installer-coreclr-Linux_musl_x64-Release - Can_Run_App_With_StatiHostError message:
System.ComponentModel.Win32Exception : Text file busy Stack trace at System.Diagnostics.Process.ForkAndExecProcess(String filename, String[] argv, String[] envp, String cwd, Boolean redirectStdin, Boolean redirectStdout, Boolean redirectStderr, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec) at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo) at System.Diagnostics.Process.Start() at Microsoft.DotNet.Cli.Build.Framework.Command.Start() in /_/src/installer/tests/TestUtils/Command.cs:line 199 at Microsoft.DotNet.Cli.Build.Framework.Command.Execute(Boolean fExpectedToFail) in /_/src/installer/tests/TestUtils/Command.cs:line 239 at Microsoft.DotNet.Cli.Build.Framework.Command.Execute() in /_/src/installer/tests/TestUtils/Command.cs:line 171 at AppHost.Bundle.Tests.StaticHost.Can_Run_App_With_StatiHost() in /_/src/installer/tests/Microsoft.NET.HostModel.Tests/AppHost.Bundle.Tests/StaticHost.cs:line 27Happening every 3rd day for this test, but IIRC there were other tests with this issue.
We've fundamentally changed how single-file tests work over the past year or two (in a way that should help with reliability). Closing this - we'll track any new failures separately.
Reacted by Adeel Mujahid- locked and limited conversation to collaborators
on Sep 20, 2024
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsNo status
In my PR, the test has failed with the following stack trace:
It looks similar to #35068
Runfo Tracking Issue: Runtime test Can_Run_App_With_StatiHost
Build Result Summary