-
Notifications
You must be signed in to change notification settings - Fork 10.3k
[release/3.1] Update dependencies from dotnet/efcore dotnet/aspnetcore-tooling #18363
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
[release/3.1] Update dependencies from dotnet/efcore dotnet/aspnetcore-tooling #18363
Conversation
…114.5 - Microsoft.EntityFrameworkCore.Tools - 3.1.2 - Microsoft.EntityFrameworkCore.SqlServer - 3.1.2 - dotnet-ef - 3.1.2 - Microsoft.EntityFrameworkCore - 3.1.2 - Microsoft.EntityFrameworkCore.InMemory - 3.1.2 - Microsoft.EntityFrameworkCore.Relational - 3.1.2 - Microsoft.EntityFrameworkCore.Sqlite - 3.1.2
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
…build 20200114.7 - Microsoft.AspNetCore.Mvc.Razor.Extensions - 3.1.2 - Microsoft.AspNetCore.Razor.Language - 3.1.2 - Microsoft.CodeAnalysis.Razor - 3.1.2 - Microsoft.NET.Sdk.Razor - 3.1.2
Template test failures look real:
@dougbu could you take a look? |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@wtgodbe that problem isn't specific to this branch. suggest working backward through the rolling or official builds to see when it was introduced (today). |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
First place I'm seeing it is in the internal build for #18357, but that PR had the template tests pass. Will take a closer look |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
Also CC @JunTaoLuo in case anything stands out |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
…build 20200115.8 - Microsoft.AspNetCore.Mvc.Razor.Extensions - 3.1.2 - Microsoft.AspNetCore.Razor.Language - 3.1.2 - Microsoft.CodeAnalysis.Razor - 3.1.2 - Microsoft.NET.Sdk.Razor - 3.1.2
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
Suspect the templates problem is not specifically coming from #18357. If the previous official or rolling build succeeded, need to check all the commits merged between them (we don't run multiple builds of any branch in parallel). |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
I may have cracked the enigma, see #18380 |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
👀 |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
/azp run aspnetcore-ci |
Azure Pipelines successfully started running 1 pipeline(s). |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@JunTaoLuo many thanks -- you did indeed crack the enigma❕ FYI the problem was introduced in ee57a0c "Use checked-in platform manifest in 3.1.2 (#18250)" though it's not clear how that caused the test regressions. But, it's pretty clear because #18379 aka dougbu/head-B -- which went back all the way to 36e7902 "Merge pull request #18151 from dotnet/johluo/feb-branding", the last successful official build's commit -- was the only test build that avoided the many template test failures. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
I don't think ee57a0c was the issue. It failed the build since it turned ref pack generation on. The underlying problem with how assemblies were resolved must have been silently introduced earlier. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@JunTaoLuo your statement is slightly contradictory. That commit introduced the problem because it turned targeting and ref/ pack builds back on. But, I agree the root cause was deeper. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
This pull request updates the following dependencies
From https://github.com/dotnet/efcore
From https://github.com/dotnet/aspnetcore-tooling