Can_Run_App_With_StatiHost installer test failure in CI

[janvorli]

In my PR, the test has failed with the following 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 47

It looks similar to #35068

Runfo Tracking Issue: Runtime test Can_Run_App_With_StatiHost

Build	Definition	Kind	Run Name

Build Result Summary

Day Hit Count	Week Hit Count	Month Hit Count
0	0	0

Tagging subscribers to this area: @vitek-karas, @agocke
See info in area-owners.md if you want to be subscribed.

[janvorli]

Here is a link:
https://dev.azure.com/dnceng/public/_build/results?buildId=810089&view=ms.vss-test-web.build-test-results-tab&runId=25747512&resultId=100006&paneView=debug

[danmoseley]

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 27

This 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

[danmoseley]

@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?

[danmoseley]

Also note this was Installer-coreclr-Linux_musl_x64-Release

[danmoseley]

This message apparently means that we are trying to execute an executable while it is being modified - apparently in its text section.

[jaredpar]

This is failing about once a day right now so blocking clean CI is appropriate here.