-
Notifications
You must be signed in to change notification settings - Fork 375
Include Dependency Frameworks in set of TFMs considered for package testing #7645
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
Conversation
src/Microsoft.DotNet.PackageTesting.Tests/GetCompatibilePackageTargetFrameworksTests.cs
Show resolved
Hide resolved
Tested locally and this does catch the windows compat bug:
Also found a new failure:
Here we'll just need to disable that project since it's expected that a single build isn't producing all these packages. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just need a test in place.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Thanks @Anipik. I merged dotnet/runtime#55976 so we should be ready to accept this change. It's still possible that new failures are introduced. @missymessa let us know if you see any dotnet/runtime failures around package testing during arcade ingestion. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fixes dotnet/runtime#27503
I believe this should fix testing for meta-packages as it will consider Frameworks for testing if they are used in dependency groups (not just files).
I haven't been able to try this out in dotnet/runtime yet and would want to do so before merging.