-
Notifications
You must be signed in to change notification settings - Fork 275
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
jmh normalizes jar timestamps #396
Conversation
build_is_identical e2e test spits out differences in md5
👍 |
@johnynek thanks! |
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.
yeah. that's the right default.
I mean, I'm not even sure we should permit this code to not normalize. That's the whole point here. But we don't have to change it to remove setNormalize for now.
only mac builds haven't run due to travis ongoing mac issues, I've run locally on a mac and merging |
Issues referenced for building in MAC (bazelbuild#136, bazelbuild#396 and bazelbuild#398) are closed/merged Having the comment `This doesn't currently pass on OS X (see bazelbuild#136 for details)` is not accurate. BTW, I cannot confirm it's true, cause in my env have bazel 0.14 and `test_all.sh` is failing (`bazel test //test/...` is OK)
Issues referenced for building in MAC (#136, #396 and #398) are closed/merged Having the comment `This doesn't currently pass on OS X (see #136 for details)` is not accurate. BTW, I cannot confirm it's true, cause in my env have bazel 0.14 and `test_all.sh` is failing (`bazel test //test/...` is OK)
additionally build_is_identical e2e test spits out differences in specific jar md5 files and not only the change in all of them. Actually useful for debugging reproducibility problems