-
-
Notifications
You must be signed in to change notification settings - Fork 992
Multiple nuget warnings/errors after moving to 0.13.6 breaking the build #2377
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
Comments
@olstakh Can you please try the latest nightly feed? https://benchmarkdotnet.org/articles/guides/nuget.html#nightly
|
@timcassell , i had to change your proposed version to 0.13.7-nightly.20230721**.42**, and it's working! |
I suspect it was due to #2369. You can continue to use 0.13.5 until 0.13.7 is released. |
@timcassell , understood. the issue you mentioned doesn't seem to be related, the variable was used for convenience only, the repro works without it. |
I'm not sure, but you can clone the repo and reference it locally. |
@olstakh the full list of available nightly packages can be found at the bottom of this page: https://www.myget.org/feed/benchmarkdotnet/package/nuget/BenchmarkDotNet |
Thanks, @AndreyAkinshin ! I found the version that was not failing with this repo any more, it's 0.13.7-nightly.20230717.35 |
The only workaround would be to remove all properties from Expect 0.13.7 to be released next week. |
When moving to the latest 0.13.6 benchmark version - we observe new nuget warnings that break our builds
Minimal repro: https://github.com/olstakh/BenchmarkBuildFailure/tree/main
Packages.Prop file has BenchmarkVersion variable defined, set to 0.13.5
When running
from the root - no warnings/errors, benchmark is executed, report is produced
After changing BenchmarkVersion in Packages.Prop file to 0.13.6 and running the same command:
The final error NU1202 seems to be the one breaking the build (with a package version that we're not referencing).
The above errors do not exist with 0.13.5.
when providing --logBuildOutput switch with 0.13.5 version, below is what displayed:
The text was updated successfully, but these errors were encountered: