[release/5.0] Update dependencies from dotnet/arcade #41038
Conversation
![dotnet-maestro[bot]](https://avatars.githubusercontent.com/in/16706?s=60&v=4){kind=small}
…817.6 Microsoft.DotNet.XUnitExtensions , Microsoft.DotNet.GenFacades , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.SharedFramework.Sdk , Microsoft.DotNet.Build.Tasks.TargetFramework.Sdk , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.GenAPI , Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.ApiCompat From Version 5.0.0-beta.20407.3 -> To Version 5.0.0-beta.20417.6
|
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
|
@safern Whatever fixes going into the arcade update in master will also need to go here too |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
|
Sounds good. Working on it. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
…819.21 Microsoft.DotNet.GenFacades , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.SharedFramework.Sdk , Microsoft.DotNet.Build.Tasks.TargetFramework.Sdk , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.GenAPI , Microsoft.DotNet.XUnitExtensions , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.ApiCompat From Version 5.0.0-beta.20417.5 -> To Version 5.0.0-beta.20419.21
|
Linq tests timeout is #41114 |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
|
@danmosemsft What about these recent failures? Issue or good to merge? |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
|
These are CLR tests. @mangod9 can someone please take a look and see whether they should block code flow? This needs to go in to unblock 5.0 flow so that Bing can consume us . Two of them seem to be can't find cmd.exe maybe a PATH issue. The other is a hang on a threading test. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
|
The errors in coreclr seem similar to an issue that's in first responders right now, where the path is getting corrupted. I see this in the tests:
|
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@hoyosjs Which issue is this? I can't find it offhand. |
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.
|
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
|
@safern I hadn't seen this one. I handpicked a few of them from different legs and all were cmd not found. The problem is the path is getting to ridiculous lengths, and in what you just sent me I can see
(also, not sure what that D%\ is meant to be... |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
😄 @MattGal do you have an idea? |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
|
@danmosemsft sorry I am OOF this week so just noticed this. Adding @trylek @jeffschwMSFT to determine whether CLR test failures are blocking. |
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.
|
|
@hoyosjs Since this appears to not be caused by this PR (given other non arcade PRs are seeing this), can we merge this to unblock 5.0? Currently it's pretty much completely blocked. |
safern
deleted the
darc-release/5.0-bdda842d-f16f-483a-96c3-e41a5960fbe7
branch
|
Went ahead and merged given that we're seeing this on other PRs. |
|
Details in https://github.com/dotnet/core-eng/issues/10586 and https://github.com/dotnet/core-eng/issues/10578 ; ASP is working to port the fix to other places when they can, and we'll get our workaround done this week. |
ghost
locked as resolved and limited conversation to collaborators
This pull request updates the following dependencies
From https://github.com/dotnet/arcade