-
Notifications
You must be signed in to change notification settings - Fork 10.3k
[master] Update dependencies from aspnet/AspNetCore-Tooling aspnet/Blazor #11307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[master] Update dependencies from aspnet/AspNetCore-Tooling aspnet/Blazor #11307
Conversation
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
…build 20190617.1 - Microsoft.NET.Sdk.Razor - 3.0.0-preview7.19317.1 - Microsoft.CodeAnalysis.Razor - 3.0.0-preview7.19317.1 - Microsoft.AspNetCore.Razor.Language - 3.0.0-preview7.19317.1 - Microsoft.AspNetCore.Mvc.Razor.Extensions - 3.0.0-preview7.19317.1
…617.1 - Microsoft.AspNetCore.Blazor.Mono - 0.10.0-preview7.19317.1
a6295b0
to
f3a3559
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look fine. Will
… rebase on 'master' to (hopefully) clean up timeouts. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
…build 20190619.3 - Microsoft.NET.Sdk.Razor - 3.0.0-preview7.19319.3 - Microsoft.CodeAnalysis.Razor - 3.0.0-preview7.19319.3 - Microsoft.AspNetCore.Razor.Language - 3.0.0-preview7.19319.3 - Microsoft.AspNetCore.Mvc.Razor.Extensions - 3.0.0-preview7.19319.3
@dougbu Do you know roughly when we should expect the latest from aspnetcore-tooling to appear in aspnetcore? I'm waiting for the changes in dotnet/razor@6e54900 to reach aspnetcore so I can finish my preview 7 work. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
…build 20190620.1 - Microsoft.NET.Sdk.Razor - 3.0.0-preview7.19320.1 - Microsoft.CodeAnalysis.Razor - 3.0.0-preview7.19320.1 - Microsoft.AspNetCore.Razor.Language - 3.0.0-preview7.19320.1 - Microsoft.AspNetCore.Mvc.Razor.Extensions - 3.0.0-preview7.19320.1
@SteveSandersonMS feel free to retry AzDO builds and triage build failures to confirm nothing is newly-bad here. I'm not on top of this and likely won't be back at it 'til Monday. @JunTaoLuo may be able to help or (say) @NTaylorMullen for timezone support from your team. |
Actually, I'll review the Helix failures and get this in (I hope). Have a minute… |
@jkotalik @JunTaoLuo every failing test has .IIS. somewhere in its full name. The tests are failing only on Windows.7.Amd64.Open and Windows.81.Amd64.Open Helix queues. Is this a known issue? |
This comment was made automatically. If there is a problem contact [email protected]. I've triaged the above build. I've created/commented on the following issue(s) |
Hm I thought I was going crazy when identifying why helix was failing. Can you check and see if these tests were failing after the arcade merge? I’m OOF tomorrow so if someone could take a look. I believe it’s an issue with finding dotnet. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
…build 20190620.3 - Microsoft.NET.Sdk.Razor - 3.0.0-preview7.19320.3 - Microsoft.CodeAnalysis.Razor - 3.0.0-preview7.19320.3 - Microsoft.AspNetCore.Razor.Language - 3.0.0-preview7.19320.3 - Microsoft.AspNetCore.Mvc.Razor.Extensions - 3.0.0-preview7.19320.3
Would be possible to look at the various build start timestamps and compare them to when the Arcade merge went in. But, not something I can do here in a timely fashion. Separately, has something about these tests changed since the Arcade merge that rerunning would be worthwhile? I'll kick off another build just in case. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
oh already running anew due to another tooling update |
Auto-Merge StatusThis pull request has been merged because the following merge policies have succeeded.
|
This pull request updates the following dependencies
From https://github.com/aspnet/AspNetCore-Tooling
From https://github.com/aspnet/Blazor