Skip to content

[release/3.0] Update dependencies from dotnet/arcade aspnet/Blazor #17270

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

Merged

Conversation

dotnet-maestro[bot]
Copy link
Contributor

@dotnet-maestro dotnet-maestro bot commented Nov 20, 2019

This pull request updates the following dependencies

From https://github.com/dotnet/arcade

  • Build: 20191119.2
  • Date Produced: 11/19/2019 6:14 PM
  • Commit: e34d933e18ba1cd393bbafcb6018e0f858d3e89e
  • Branch: refs/heads/release/3.x
  • Updates:
    • Microsoft.DotNet.Arcade.Sdk -> 1.0.0-beta.19569.2
    • Microsoft.DotNet.GenAPI -> 1.0.0-beta.19569.2
    • Microsoft.DotNet.Helix.Sdk -> 2.0.0-beta.19569.2

From https://github.com/aspnet/Blazor

  • Build: 20191120.2
  • Date Produced: 11/20/2019 9:04 PM
  • Commit: a10163f767cf263d593836c9249d8314e8948d89
  • Branch: refs/heads/release/3.0
  • Updates:
    • Microsoft.AspNetCore.Blazor.Mono -> 3.0.0-preview9.19570.2

…119.2

- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19569.2
- Microsoft.DotNet.GenAPI - 1.0.0-beta.19569.2
- Microsoft.DotNet.Helix.Sdk - 2.0.0-beta.19569.2
@dotnet-maestro dotnet-maestro bot requested review from dougbu and a team as code owners November 20, 2019 19:34
@dotnet-maestro
Copy link
Contributor Author

dotnet-maestro bot commented Nov 20, 2019

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

  • All Checks Successful Unsuccessful checks: AspNetCore-ci (Build Test: Windows Server 2016 x64)
  • ✔️ No Requested Changes Succeeded - No reviews have requested changes.

…120.2

- Microsoft.AspNetCore.Blazor.Mono - 3.0.0-preview9.19570.2
@dotnet-maestro dotnet-maestro bot changed the title [release/3.0] Update dependencies from dotnet/arcade [release/3.0] Update dependencies from dotnet/arcade aspnet/Blazor Nov 20, 2019
@ajaybhargavb
Copy link
Contributor

Test failure,

InputDateInteractsWithEditContext_NullableDateTimeOffset

Assert.Equal() Failure\r\nExpected: modified invalid\r\nActual: modified valid

at Microsoft.AspNetCore.E2ETesting.WaitAssert.<>c__DisplayClass11_0.<WaitAssertCore>b__0(IWebDriver _) in /_/src/Shared/E2ETesting/WaitAssert.cs:line 72
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.E2ETesting.WaitAssert.WaitAssertCore(IWebDriver driver, Action assertion, TimeSpan timeout) in /_/src/Shared/E2ETesting/WaitAssert.cs:line 91
   at Microsoft.AspNetCore.E2ETesting.WaitAssert.Equal[T](IWebDriver driver, T expected, Func`1 actual) in /_/src/Shared/E2ETesting/WaitAssert.cs:line 21
   at Microsoft.AspNetCore.Components.E2ETest.Tests.FormsTest.InputDateInteractsWithEditContext_NullableDateTimeOffset() in /_/src/Components/test/E2ETest/Tests/FormsTest.cs:line 233

@pranavkm @SteveSandersonMS, have you seen this before? Can you take a look?

@dotnet-maestro
Copy link
Contributor Author

dotnet-maestro bot commented Nov 20, 2019

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

  • All Checks Successful Unsuccessful checks: AspNetCore-ci (Build Test: Windows Server 2016 x64)
  • ✔️ No Requested Changes Succeeded - No reviews have requested changes.

@SteveSandersonMS
Copy link
Member

Yes, this test has been a problem for us for a long time. The most recent person looking into it (there have been many) is @ryanbrandenburg (as in https://github.com/aspnet/AspNetCore-Internal/issues/3295#issuecomment-555196029). Ryan, are you planning to mark this test as flaky?

@dotnet-maestro
Copy link
Contributor Author

dotnet-maestro bot commented Nov 20, 2019

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

  • All Checks Successful Unsuccessful checks: AspNetCore-ci, AspNetCore-ci (Build Test: Windows Server 2016 x64)
  • ✔️ No Requested Changes Succeeded - No reviews have requested changes.

@ryanbrandenburg
Copy link
Contributor

I don't have much context on tests like InputDateInteractsWithEditContext_NonNullableDateTime, but it doesn't appear to be a single test with this problem, it's a class of tests starting with InputDate, which we would have to mark all Flaky. If you as someone who knows that area are fine with losing that coverage I can make the change. I just want to be sure we understand what we're getting into.

@dotnet-maestro
Copy link
Contributor Author

dotnet-maestro bot commented Nov 21, 2019

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

  • All Checks Successful Unsuccessful checks: AspNetCore-ci, AspNetCore-ci (Build Test: Windows Server 2016 x64)
  • ✔️ No Requested Changes Succeeded - No reviews have requested changes.

Copy link
Contributor

@dougbu dougbu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not merging 'til @mmitche confirms the file deletions are correct and the test failures are resolved

@dougbu
Copy link
Contributor

dougbu commented Nov 21, 2019

and the test failures are resolved

Should mention I retried the failed jobs in https://dev.azure.com/dnceng/public/_build/results?buildId=433505 Hopefully the next attempt won't hit a different flaky-but-not-so-marked test failure.

@dotnet-maestro
Copy link
Contributor Author

dotnet-maestro bot commented Nov 21, 2019

Auto-Merge Status

This pull request will be merged because the following merge policies have succeeded.

  • ✔️ All Checks Successful Succeeded - Successful checks: AspNetCore-ci, AspNetCore-ci (Build Test: Windows Server 2016 x64), AspNetCore-ci (Build Test: Linux Source Build), AspNetCore-ci (Build Test: Ubuntu 16.04 x64), AspNetCore-ci (Build Test: Templates - Windows Server 2016 x64), AspNetCore-ci (Build Test: macOS 10.13), AspNetCore-ci (Build Build: Linux Musl ARM64), AspNetCore-ci (Build Build: Linux x64), AspNetCore-ci (Build Build: Linux Musl x64), AspNetCore-ci (Build Build: Linux ARM64), AspNetCore-ci (Build Build: Linux ARM), AspNetCore-ci (Build Build: macOS), AspNetCore-ci (Build Build: Windows ARM), AspNetCore-ci (Build Code check), AspNetCore-ci (Build Build: Windows x64/x86)
  • ✔️ No Requested Changes Succeeded - No reviews have requested changes.

@dougbu dougbu merged commit 43ca89b into release/3.0 Nov 21, 2019
@dougbu dougbu deleted the darc-release/3.0-5a103f41-c1e5-4032-9421-ee68a21173fa branch November 21, 2019 03:51
@dougbu
Copy link
Contributor

dougbu commented Nov 21, 2019

Got this in because @mmitche confirmed elsewhere that deleting a few eng/common/** files all good and the validation build completed successfully.

@dougbu dougbu added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Nov 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants