-
Notifications
You must be signed in to change notification settings - Fork 4.9k
[master] Update dependencies from dotnet/coreclr #36480
[master] Update dependencies from dotnet/coreclr #36480
Conversation
…0328.73 - Microsoft.NET.Sdk.IL - 3.0.0-preview4-27528-73 - Microsoft.NETCore.ILAsm - 3.0.0-preview4-27528-73 - Microsoft.NETCore.Runtime.CoreCLR - 3.0.0-preview4-27528-73
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
Linux is just Fedora 27 and can be ignored. Windows is fishier. Several failures in serialization tests. In the XML ones, this is throwing
that type definition public struct StructNotSerializable
{
public int value;
public override int GetHashCode()
{
return value;
}
} The default implementation of @jkotas thoughts? |
The JSON ones look likely the same cause. |
Any why didn't these tests fail in CoreCLR... |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
This is failing on x86 only. We do not run CoreFX on x86 in CoreCLR CI today. Fixing that is on the list of coverage tweaks that I have talked with @RussKeldorph . |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@briansull FYI |
Given that this fails on x86 only, this break is likely introduced by dotnet/coreclr#22255 . @CarolEidt Could you please take a look? (Let me know if you need help with isolating a small repro.) |
@jkotas - I'm tracking down another test failure due to dotnet/coreclr#22255. This may or may not be the same root cause, but if you have some time to get a small repro, it would be greatly appreciated. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@CarolEidt Here is a small repro: Repros on x86 only Actual result: 0 15
|
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
…0329.71 - Microsoft.NET.Sdk.IL - 3.0.0-preview4-27529-71 - Microsoft.NETCore.ILAsm - 3.0.0-preview4-27529-71 - Microsoft.NETCore.Runtime.CoreCLR - 3.0.0-preview4-27529-71
…0331.71 - Microsoft.NET.Sdk.IL - 3.0.0-preview4-27531-71 - Microsoft.NETCore.ILAsm - 3.0.0-preview4-27531-71 - Microsoft.NETCore.Runtime.CoreCLR - 3.0.0-preview4-27531-71
Thanks @jkotas for the repro test case - I've verified that it's fixed with my fix for https://github.com/dotnet/coreclr/issues/23545, and have added that test case to the PR (dotnet/coreclr#23570) |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
…0401.72 - Microsoft.NET.Sdk.IL - 3.0.0-preview4-27601-72 - Microsoft.NETCore.ILAsm - 3.0.0-preview4-27601-72 - Microsoft.NETCore.Runtime.CoreCLR - 3.0.0-preview4-27601-72
The repro case that @jkotas provided has been fixed with dotnet/coreclr#23570 |
Auto-Merge StatusThis pull request will be merged because the following merge policies have succeeded.
|
…0402.72 - Microsoft.NET.Sdk.IL - 3.0.0-preview4-27602-72 - Microsoft.NETCore.ILAsm - 3.0.0-preview4-27602-72 - Microsoft.NETCore.Runtime.CoreCLR - 3.0.0-preview4-27602-72
Conflicts. Closing. |
This pull request updates the following dependencies
From https://github.com/dotnet/coreclr
From https://github.com/dotnet/coreclr
From https://github.com/dotnet/coreclr
From https://github.com/dotnet/coreclr
From https://github.com/dotnet/coreclr
From https://github.com/dotnet/coreclr