-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Fix SR-4659 Benchmark logs should be tied to tested tree version #8978
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
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.
Your feedback on 1 small change. Otherwise, it looks fine to me.
`git_repo_path`""" | ||
return subprocess.check_output( | ||
['git', '-C', git_repo_path, 'rev-parse', | ||
'--short', 'HEAD'], stderr=subprocess.STDOUT).strip() |
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.
Can you use the full hash here? The reason why is that over time as history grows, a prefix collision becomes much more likely to happen. I have noticed this happen a few times with swift recently. It would be unfortunate if this was attached to a bug report and we could not tell the exact revision that it came from. That being said, I am not that wedded to this if you think I am being too paranoid.
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.
I didn't want to make the log filename overly long. Currently we have:
Benchmark_O-20170421004027.log
my change makes it:
Benchmark_O-20170422050121-077340abd7.log
full hash would be IMHO unwieldy:
Benchmark_O-20170422050121-f3b33f06d4c60f70afc591f2d261e7aac1c5d0ac.log
In SR-4675 "Report detailed build version from Benchmark drivers" I plan to report full hash and will add it into the report itself. So that will take care of that.
Also, there will be no conflicts with this - filename is still unique due to timestamp.
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.
Ok. I am fine with that.
@swift-ci smoke benchmark |
Build comment file:Optimized (O) Regression (0)Improvement (0)No Changes (268)
Regression (0)Improvement (2)
No Changes (266)
|
@swift-ci smoke test and merge |
@gottesmm I’ve fixed the missing whitespace lint complained about, amended and force pushed. Can you smoke test and merge again, please? |
@swift-ci smoke test and merge |
Resolves SR-4659.
Broken out of #8793.
@gottesmm Please review.