-
Notifications
You must be signed in to change notification settings - Fork 10.3k
[release/2.1] transitive dependencies aren't lifted for tests in patch builds #29023
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
Labels
area-infrastructure
Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Done
This issue has been fixed
Comments
dougbu
added a commit
that referenced
this issue
Jan 19, 2021
- #29023 - ensure tests do not use baseline assemblies for projects in current patch
dougbu
added a commit
that referenced
this issue
Jan 26, 2021
- #29023 - ensure tests do not use baseline assemblies for projects in current patch
dougbu
added a commit
that referenced
this issue
Jan 27, 2021
- #29023 - ensure tests do not use baseline assemblies for projects in current patch
dougbu
added a commit
that referenced
this issue
Jan 28, 2021
- #29023 - ensure tests do not use baseline assemblies for projects in current patch
dougbu
added a commit
that referenced
this issue
Feb 10, 2021
- #29023 - ensure tests do not use baseline assemblies for projects in current patch
My thanks to @Tratcher who made me aware of this issue |
🥳 I can break tests again. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area-infrastructure
Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Done
This issue has been fixed
Imagine a test project
Test
, which referencesProject1
, which referencesProject2
. If we make a functional change toProject2
in a patch, the test project will not consume the updated project - it only consumes the live-built version of its direct dependencies. The transitive dependencies get resolved from the baseline, which points to the latest public version on nuget.org. We should check to make sure that this understanding of our behavior is accurate, and either tweak our logic or our testing policy in 2.1 to account for it.CC @dotnet/aspnet-build
The text was updated successfully, but these errors were encountered: