-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[master] Update dependencies from nuget/nuget.client #11188
[master] Update dependencies from nuget/nuget.client #11188
Conversation
…5.6.0.6558 - NuGet.Build.Tasks - 5.6.0-preview.3.6558
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@dsplaisted @wli3 build here is failing because we're being warned that there's an implicit reference to Microsoft.NETFramework.ReferenceAssemblies. Do we want to stop treating this warning as an error or should I make a patch to #10981 to not include the implicit package reference if there's an explicit one? |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@sfoslund I think if we can we should update the logic so that it will only add the implicit reference if there's not an explicit one already. I probably should have caught that in the code review. If we're blocked on updating dependencies due to this, we can temporarily ignore the warning (or maybe just remove the explicit PackageReferences to the reference assembly package). |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@dsplaisted I'll try to get a fix out to master by EOD today, but it's too late for prev 3, right? If we need to update stage 0 in prev 3 then we'll likely run into this issue and have to temporarily ignore the warning. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
…5.7.0.6568 - NuGet.Build.Tasks: 5.6.0-preview.2.6532 -> 5.7.0-preview.1.6568
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@sfoslund Are you looking at this? It looks like it may now be failing with a different problem:
|
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@dsplaisted I think stage 0 needs to be updated to get the changes from #11242, but as the official build is broken I haven't been able to do that. dotnet/arcade#5329 is tracking the issue with the official build. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@sfoslund Do we have successful official builds by now that we can use to update stage 0? |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
This build was the first to succeed in the publishing step https://dev.azure.com/dnceng/internal/_build/results?buildId=619386&view=results but we've been seeing CopyToLatest issues as well. There's some discussion of fixes for this on the original arcade issue, see this comment: dotnet/arcade#5329 (comment). |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
I'm taking care of the "copy to latest" failure in dotnet/installer#7327. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
…5.7.0.6592 - NuGet.Build.Tasks: 5.6.0-preview.2.6532 -> 5.7.0-preview.1.6592
@dsplaisted the build warnings caused by the ref assemblies are resolved but we're seeing some publishing test failures. These are the failing tests:
Do you recognize any of the errors? |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@sfoslund can you please update stage 0 to |
no @zivkan. I missed "Always update to the latest darc before publishing!" instruction in our OneNote doc. Can I execute the commands again after updating the darc automation tool ? |
No need. I ran them. I first removed the build from the channels and re-added it:
|
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@mmitche - can the darc tool be made so that old versions don't let you run them? |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
I'm opposed to this, as there is a release of darc almost every week. Most darc functionality doesn't change release to release, so disabling usage of those darc is pretty crappy (also there are offline scenarios where darc can't contact to do an up to date check anyway). It's really just in this case that the darc version that was being used is very old (at least 3-4 months?) and doesn't even have the required capabilities. Newer darc versions will tell you if they aren't compatible. |
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.
|
Hopefully this will fix flaky failures for this test
ItRestoresLibToSpecificDirectory seems to be failing again (similar to some previous insertions). Given the test name, I'm wondering if there could be an environment variable set that makes this fail occassionaly. The variables to look at are: NUGET_PACKAGES or RestorePackagesPath, which is the MSBuild property NuGet reads. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@nkolev92 I've updated the test to dump the assets file contents if the assertion fails. Would that be likely to contain information to help understand the failures? |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
Yeah, that should help. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
8bed5eb
to
15742b6
Compare
Looking at the assets file from the CI run, it looks like the problem is that the test is creating a .NET 5 class library, which doesn't depend on any package references. When I run it locally in VS however, it creates a .NET Standard 2.0 class library, which does depend on some packages, so the test passes. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@wli3 OK, so the reason this wasn't failing locally for any of us is because locally we use v5.0.100-dev for the SDK version, and once the classlib template had been populated in that folder in .templateengine, it doesn't get updated when the template changes (ie from targeting .NET Standard 2.0 to .NET 5). Isolating DOTNET_CLI_HOME to the repo could help with this (though you would still probably need to delete the folder in the local artifacts folder). |
Auto-Merge StatusThis pull request has been merged because the following merge policies have succeeded.
|
Classlib template now targets .NET 5 which doesn't require any implicit package references
yay 🥳 🥳 🥳 🥳 🥳 🥳 🥳 🥳 🥳 🥳 🥳 🥳 🥳 🥳 🥳 🎈 🎈 🎈🎈 🎈 🎈🎈 🎈 🎈🎈 🎈 🎈🎈 🎈 🎈🎈 🎈 🎈 |
@mmitche - I am unable to locate quickly if there was any PR created in dotnet/cli repo for this insertion. I found a PR in .NET CLI repo for previous insertion but not for the current one.
/cc @donnie-msft |
@mmitche - Thanks you for helping us by creating a PR insertion in to CLI repo dotnet/cli#13358 |
This pull request updates the following dependencies
From https://github.com/NuGet/NuGet.Client