Uh oh!
There was an error while loading. Please reload this page.
[master] Update dependencies from dotnet/arcade dotnet/runtime-assets - #33562
Conversation
…312.3 - Microsoft.DotNet.XUnitExtensions - 5.0.0-beta.20162.3 - Microsoft.DotNet.VersionTools.Tasks - 5.0.0-beta.20162.3 - Microsoft.DotNet.ApiCompat - 5.0.0-beta.20162.3 - Microsoft.DotNet.Arcade.Sdk - 5.0.0-beta.20162.3 - Microsoft.DotNet.Build.Tasks.Feed - 5.0.0-beta.20162.3 - Microsoft.DotNet.Build.Tasks.Packaging - 5.0.0-beta.20162.3 - Microsoft.DotNet.Build.Tasks.SharedFramework.Sdk - 5.0.0-beta.20162.3 - Microsoft.DotNet.Build.Tasks.TargetFramework.Sdk - 5.0.0-beta.20162.3 - Microsoft.DotNet.CodeAnalysis - 5.0.0-beta.20162.3 - Microsoft.DotNet.GenAPI - 5.0.0-beta.20162.3 - Microsoft.DotNet.GenFacades - 5.0.0-beta.20162.3 - Microsoft.DotNet.Helix.Sdk - 5.0.0-beta.20162.3 - Microsoft.DotNet.RemoteExecutor - 5.0.0-beta.20162.3 - Microsoft.DotNet.XUnitConsoleRunner - 2.5.1-beta.20162.3
wtgodbe
commented
Mar 13, 2020
With any luck this should unblock official builds of runtime, which should unblock dotnet/extensions#3077. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
…ld 20200312.1 - System.Windows.Extensions.TestData - 5.0.0-beta.20162.1 - System.Security.Cryptography.X509Certificates.TestData - 5.0.0-beta.20162.1 - System.Private.Runtime.UnicodeData - 5.0.0-beta.20162.1 - System.Net.TestData - 5.0.0-beta.20162.1 - System.IO.Packaging.TestData - 5.0.0-beta.20162.1 - System.IO.Compression.TestData - 5.0.0-beta.20162.1 - System.Drawing.Common.TestData - 5.0.0-beta.20162.1 - System.ComponentModel.TypeConverter.TestData - 5.0.0-beta.20162.1
wtgodbe
commented
Mar 13, 2020
Actually, there's still one more fix needed to unblock the builds of runtime - dotnet/arcade#5053 (comment) |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
GrabYourPitchforks
commented
Mar 13, 2020
CI is failing: .packages/microsoft.dotnet.apicompat/5.0.0-beta.20162.3/build/Microsoft.DotNet.ApiCompat.targets(143,5): error : MembersMustExist : Member 'System.AppContext.add_FirstChanceException(System.EventHandler<System.Runtime.ExceptionServices.FirstChanceExceptionEventArgs>)' does not exist in the reference but it does exist in the implementation. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
wtgodbe
commented
Mar 13, 2020
There were some changes to APICompat yesterday: dotnet/arcade@a5a6a98 @gugavaro could this impact what checks are triggered? CC @ericstj |
wtgodbe
commented
Mar 13, 2020
Also CC @safern@Anipik@ViktorHofer |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
safern
commented
Mar 13, 2020
This was expected to happen and I believe @gugavaro already has the needed changes ready. Could you please push them to this PR 😄 ? |
ericstj
commented
Mar 13, 2020
I believe we already merged them. Just need to rerun against tip. |
safern
commented
Mar 13, 2020
Yeah I saw that now: 4480bdb I'll re-run. |
| <MicrosoftDotNetBuildTasksPackagingVersion>5.0.0-beta.20160.4</MicrosoftDotNetBuildTasksPackagingVersion> | ||
| <MicrosoftDotNetRemoteExecutorVersion>5.0.0-beta.20160.4</MicrosoftDotNetRemoteExecutorVersion> | ||
| <MicrosoftDotNetVersionToolsTasksVersion>5.0.0-beta.20160.4</MicrosoftDotNetVersionToolsTasksVersion> | ||
| <MicrosoftDotNetApiCompatVersion>5.0.0-beta.20162.3</MicrosoftDotNetApiCompatVersion> |
There was a problem hiding this comment.
Actually, it looks like this is downgrading the APIComat version? 😖
There was a problem hiding this comment.
Yeah, just noticed that as well. It seems like maybe the .4 hasn't made it to the Latest channel and it is still in Validation. Will remove that change in a sec.
There was a problem hiding this comment.
Weird - the version in details.xml was 5.0.0-beta.20160.4, not 5.0.0-beta.20162.4
There was a problem hiding this comment.
It seems like it was because we updated it manually but we didn't update details.xml
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
safern
commented
Mar 13, 2020
Fixed. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
safern
commented
Mar 13, 2020
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
jkotas
commented
Mar 13, 2020
I have not see it. Do you see the same failures in the rolling builds on master? |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
safern
commented
Mar 13, 2020
Yeah I see it. It seems like it started happening in: https://dev.azure.com/dnceng/public/_build/results?buildId=557918 Looking at the commits. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
safern
commented
Mar 13, 2020
It seems like there was only 2 commits from the last successful rolling build and the first one hitting the issue. Maybe it is this one: 84cf6a1 |
jkotas
commented
Mar 13, 2020
Or the GCC change. Is it possible that we are running the tests against GCC built binaries? |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
jkotas
commented
Mar 13, 2020
The GCC leg should be build-only. No tests. |
AndyAyersMS
commented
Mar 13, 2020
I've been trying to repro the x64 linux checked failure since it hit one of my PRs. No luck so far. No crash dump from the failure either. |
jkotas
commented
Mar 13, 2020
This makes the GCC change more likely culprit. |
safern
commented
Mar 13, 2020
There is a crashdump here:
I believe it is build-only, but let me look at it. That could probably be the issue, probably the GCC leg is overriding the real coreclr artifacts. Looking now. |
Yeah. That is the issue from looking at the logs it is overriding the bin. /__w/1/a/CoreCLRProduct_Linux_x64_checked.tar.gz I'll disable the publishing of the coreclr artifacts of GCC as it is not needed. I'll put up a PR to fix it in a sec. cc: @am11 |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
AndyAyersMS
commented
Mar 13, 2020
In my CI runs, we publish two sets of test native binaries -- looks like the GCC ones overwrite the CLANG ones...? Clang build GCC build |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
safern
commented
Mar 13, 2020
Yeah. It seems like it doesn't repro all the time because it depends which leg finishes first. I put up a PR to fix it: #33580 |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
safern
commented
Mar 14, 2020
Failures are known and fixed: #33580 |
This pull request updates the following dependencies
From https://github.com/dotnet/arcade
From https://github.com/dotnet/runtime-assets