NodaTime 2.2.2 NuGet package appears to be built "non-optimized" #1027
Comments
Thanks for reporting this. I'll look into it as soon as I can. It may be a problem with the build scripts used when there's a new version of TZDB. (If that's the case, it'll mean rebuilding 2.1.1 and 2.0.4 as well...) |
Confirmed it's the debug build, by looking in ildasm - if It looks like the 1.x releases are okay, fortunately. |
Right, found the problem. It's easy to fix in the update scripts, but it'll need a little care when doing the releases, to get appropriate commit messages. |
jskeet
added a commit
to jskeet/nodatime
that referenced
this issue
Nov 15, 2017
This was referenced Nov 15, 2017
jskeet
added a commit
that referenced
this issue
Nov 15, 2017
All the new packages have now been pushed - if you update to latest, it should fix the problem. Obviously if it doesn't, please shout! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After upgrading to the NodaTime 2.2.2 NuGet package, our BenchmarkDotNet tests fail with the following error:
Reverting to any previous version works.
The text was updated successfully, but these errors were encountered: