Skip to content

Commit 265ca24

Browse files
committed
Debug dotnet new timeouts
- hang long enough to grab a dump This will _not_ help us understand later inability to acquire `DotNetNewLock` - guessing but this might have something to do w/ the 20 minute default timeout for that acquisition
1 parent b72c065 commit 265ca24

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

src/ProjectTemplates/Shared/Project.cs

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -111,8 +111,16 @@ internal async Task<ProcessResult> RunDotNetNewAsync(
111111

112112
// Temporary while investigating why this process occasionally never runs or exits on Debian 9
113113
environmentVariables.Add("COREHOST_TRACE", "1");
114-
using var execution = ProcessEx.Run(Output, AppContext.BaseDirectory, DotNetMuxer.MuxerPathOrDefault(), argString, environmentVariables);
114+
115+
using var execution = ProcessEx.Run(
116+
Output,
117+
AppContext.BaseDirectory,
118+
DotNetMuxer.MuxerPathOrDefault(),
119+
argString,
120+
environmentVariables,
121+
TimeSpan.FromHours(5));
115122
await execution.Exited;
123+
116124
return new ProcessResult(execution);
117125
}
118126
finally

0 commit comments

Comments
 (0)