Christopher Costa
Christopher Costa
Completed with https://dev.azure.com/dnceng/internal/_git/dotnet-helix-machines/pullrequest/39945
Let's take a look after the current helix outage has been resolved.
the queue has been created (I see it receiving messages in Azure). I'm not certain, but I think there might be another step required to get physical hardware connected to...
i'll take a look this afternoon
@AlitzelMendez ,appreciate you, I'll take another look
Ali was right about why deployment was failing. After temporarily changing the 'monitoredUpgrade' parameter of the [deploymentParameters]( https://dev.azure.com/dnceng/internal/_git/dotnet-helix-service?path=/eng/deployment/deploy.ps1&version=GBmain&line=81&lineEnd=82&lineStartColumn=1&lineEndColumn=1&lineStyle=plain&_a=contents) to `$false` for validation purposes (and retrying a few test failures), we...
> says they are targeting April I agree with everything Richie said, and I saw something recently that indicated they thought June was likely (I think based on historical data),...
@sbomer, is this a separate issue or just capturing the resultant behavior from #3763 not behaving as expected?
Is this specifically related to your official builds or your local dev builds? For local dev builds, this is a generally desirable behavior.
What is your expectation of behavior? As @dagood points out... > SDK rollfoward in general is intended, new to 3.0: dotnet/core-setup#6953, dotnet/designs#71. I believe that means this issue can be...