-
Notifications
You must be signed in to change notification settings - Fork 519
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
[release/6.0.1xx-preview5] Update dependencies from dotnet/installer #11672
[release/6.0.1xx-preview5] Update dependencies from dotnet/installer #11672
Conversation
…210525.1 Microsoft.Dotnet.Sdk.Internal From Version 6.0.100-preview.4.21218.6 -> To Version 6.0.100-preview.5.21275.1 Dependency coherency updates Microsoft.NET.ILLink.Tasks From Version 6.0.100-preview.2.21212.1 -> To Version 6.0.100-preview.5.21264.1 (parent: Microsoft.Dotnet.Sdk.Internal
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
🔥 Tests failed catastrophically on Build (no summary found). 🔥Result file $(TEST_SUMMARY_PATH) not found. |
dotnet/runtime#53076 is not (yet) part of the maestro bump - last commits were on May 20th |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Yeah, but it doesn't build because it seems that build didn't publish the .tar.gz file we need (which might be the same reason maestro doesn't want to update to it automatically and I had to do it manually). I think I'll just wait a few hours and see what happens. |
🔥 Tests failed catastrophically on Build (no summary found). 🔥Result file $(TEST_SUMMARY_PATH) not found. |
…210527.1 Microsoft.Dotnet.Sdk.Internal From Version 6.0.100-preview.4.21218.6 -> To Version 6.0.100-preview.5.21277.1 Dependency coherency updates Microsoft.NET.ILLink.Tasks From Version 6.0.100-preview.2.21212.1 -> To Version 6.0.100-preview.5.21264.1 (parent: Microsoft.Dotnet.Sdk.Internal
Test failures are unrelated:
|
This pull request updates the following dependencies
Coherency Updates
The following updates ensure that dependencies with a CoherentParentDependency
attribute were produced in a build used as input to the parent dependency's build.
See Dependency Description Format
From https://github.com/dotnet/installer