-
Notifications
You must be signed in to change notification settings - Fork 4.9k
[release/3.1] Update dependencies from dotnet/coreclr #42832
[release/3.1] Update dependencies from dotnet/coreclr #42832
Conversation
…0115.4 - Microsoft.NET.Sdk.IL - 3.1.2-servicing.20065.4 - Microsoft.NETCore.ILAsm - 3.1.2-servicing.20065.4 - Microsoft.NETCore.Runtime.CoreCLR - 3.1.2-servicing.20065.4
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
Lots of test failures in System.Text here - @ahsonkhan @safern @ericstj who can take a look at this? |
Presumably related to dotnet/coreclr@4e29494 - @GrabYourPitchforks PTAL |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@Anipik @GrabYourPitchforks it looks like we need to bring in the changes from #42829 does that sound correct? |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
I'm in office now, I will handle this. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
I noticed that Fedora had the same 4 failures as all the others (I looked at the text log) it just didn't report it to AzDo perhaps because of this:
@dotnet/dnceng |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@MattGal should we open an issue somewhere about Fedora machines missing Python? |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
It looks like the problem is that it's picking up Python 2, not Python 3. (Named parameters are apparently introduced in Python 3) |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
Had a quick look at the macOS failures -- the networking tests passed, but infra failed; the crypto tests left no log. Opened linked issues for both. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
Getting Helix timeouts, but we have test coverage from the other legs. |
It looks like the Windows 7 open queue failed to scale-up for several hours. It's fully scaled-up now, so I expect this is a transient Azure issue. We'll keep an eye on it. |
What about this? Is this still an issue? |
I'll open a core-eng issue for it. |
Put some notes into that issue, TL;DR: An upgrade to |
This pull request updates the following dependencies
From https://github.com/dotnet/coreclr