-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Update branding to 3.0.3 #18217
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
Update branding to 3.0.3 #18217
Conversation
…ositories This pull request updates the following dependencies [marker]: <> (Begin:24caa7fc-346f-47b4-c5c6-08d76fa9c820) ## From https://github.com/aspnet/EntityFrameworkCore - **Build**: 20191208.3 - **Date Produced**: 12/8/2019 4:22 PM - **Commit**: cd16513c90c11170f43057c9af5c75363837a742 - **Branch**: refs/heads/internal/release/3.0 - **Updates**: - **Microsoft.EntityFrameworkCore.Tools** -> 3.0.2-servicing.19608.3 - **Microsoft.EntityFrameworkCore.SqlServer** -> 3.0.2-servicing.19608.3 - **dotnet-ef** -> 3.0.2-servicing.19608.3 - **Microsoft.EntityFrameworkCore** -> 3.0.2-servicing.19608.3 - **Microsoft.EntityFrameworkCore.InMemory** -> 3.0.2-servicing.19608.3 - **Microsoft.EntityFrameworkCore.Relational** -> 3.0.2-servicing.19608.3 - **Microsoft.EntityFrameworkCore.Sqlite** -> 3.0.2-servicing.19608.3 [marker]: <> (End:24caa7fc-346f-47b4-c5c6-08d76fa9c820) [marker]: <> (Begin:Coherency Updates) ## Coherency Updates The following updates ensure that dependencies with a *CoherentParentDependency* attribute were produced in a build used as input to the parent dependency's build. See [Dependency Description Format](https://github.com/dotnet/arcade/blob/master/Documentation/DependencyDescriptionFormat.md#dependency-description-overview) - **System.Drawing.Common** -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64) - **Microsoft.NETCore.Platforms** -> 3.0.0 (parent: Microsoft.NETCore.App.Runtime.win-x64) [marker]: <> (End:Coherency Updates)
…ositories This pull request updates the following dependencies [marker]: <> (Begin:84a76f0f-36f1-4cd1-d435-08d76e1d3434) ## From https://dev.azure.com/dnceng/internal/_git/aspnet-AspNetCore-Tooling - **Build**: 20191214.13 - **Date Produced**: 12/15/2019 3:31 AM - **Commit**: 7dfb8241da14b065a0453b969c570a6736f31b54 - **Branch**: refs/heads/internal/release/3.0 - **Updates**: - **Microsoft.NET.Sdk.Razor** -> 3.0.2 - **Microsoft.CodeAnalysis.Razor** -> 3.0.2 - **Microsoft.AspNetCore.Razor.Language** -> 3.0.2 - **Microsoft.AspNetCore.Mvc.Razor.Extensions** -> 3.0.2 [marker]: <> (End:84a76f0f-36f1-4cd1-d435-08d76e1d3434) [marker]: <> (Begin:Coherency Updates) ## Coherency Updates The following updates ensure that dependencies with a *CoherentParentDependency* attribute were produced in a build used as input to the parent dependency's build. See [Dependency Description Format](https://github.com/dotnet/arcade/blob/master/Documentation/DependencyDescriptionFormat.md#dependency-description-overview) - **System.Drawing.Common** -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64) - **Microsoft.NETCore.Platforms** -> 3.0.0 (parent: Microsoft.NETCore.App.Runtime.win-x64) [marker]: <> (End:Coherency Updates)
Update dependencies. Somehow the last 3.0 EFCore update got missed.
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.
Incomplete w/o downloading the 3.0.2 packages
eng/Baseline.Designer.props
Outdated
@@ -332,11 +332,11 @@ | |||
</ItemGroup> | |||
<!-- Package: Microsoft.AspNetCore.DataProtection.EntityFrameworkCore--> | |||
<PropertyGroup Condition=" '$(PackageId)' == 'Microsoft.AspNetCore.DataProtection.EntityFrameworkCore' "> | |||
<BaselinePackageVersion>3.0.0</BaselinePackageVersion> | |||
<BaselinePackageVersion>3.0.1</BaselinePackageVersion> |
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.
Need more 3.0.2 changes before this is ready to go
We're going to be blocked on this for a while. We noticed that extensions packages were not pushed, and nuget index still hasn't updated for aspnetcore packages. |
18dcd3b
to
a8bb8dd
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.
Once the build succeeds
Yea I'm waiting until x64/x86 finishes before retrying |
@@ -47,7 +47,12 @@ function LogError { | |||
try { | |||
if ($ci) { | |||
# Install dotnet.exe | |||
& $repoRoot/restore.cmd -ci -NoBuildNodeJS -DotNetRuntimeSourceFeed $DotNetRuntimeSourceFeed -DotNetRuntimeSourceFeedKey $DotNetRuntimeSourceFeedKey | |||
if ($DotNetRuntimeSourceFeed -or $DotNetRuntimeSourceFeedKey) { |
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.
@mmitche I think this was failing since the variables DotNetRuntimeSourceFeed and DotNetRuntimeSourceFeedKey may be empty and will fail when passed to build.ps1. Does this sound right to you?
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.
We should be able to accept both cases.
So far, @anurse @jkotalik I see comments about this test in aspnet/AspNetCore-Internal@2181 but they only mention 'release/3.1'. Is it known to be flaky in 'release/3.0' as well? Basically, can we merge once the current builds complete? Or, should we wait for a Ubuntu retry? |
New test thats flaky, you can merge if it's the only failure. I'll look into fixing it |
Thanks @BrennanConroy❕ |
Shoot. Templates tests are also failing. More flakiness? If yes, probably need to retry both legs once the other jobs complete. |
Templates failures don't look like flakiness.
|
Strange, we specifically didn't build a ref pack in 3.0.2, so I'm curious why it's looking for it. |
FYI @BrennanConroy And, yes, we'll ignore it if the remaining unmarked tests pass 😺 |
https://github.com/aspnet/AspNetCore-Internal/issues/3464