-
Notifications
You must be signed in to change notification settings - Fork 110
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
Params comparison instrumentation #76
base: master
Are you sure you want to change the base?
Params comparison instrumentation #76
Conversation
…ingOnNode() : log on which node we have a hit
…ingOnNode() : log the itemParams we compare to too
…check fail (some or all actual params not hit by filter)
…ingOnNode() : log the params arrays before and after doFilter()ing
…o paramsToCompare for readability
…ility and update some comments
…spam in FINE level
d40bbd4
to
63af186
Compare
Updated for minor conflicts after #75 was merged |
@jimklimov Is there still a strong motivation to finish and merge this PR? I'm not sure if this is still useful or if it has outlived its purpose after it was used to successfully debug previous issues. If it is still needed, I'm concerned about the cost of the string concatenation for all the fine log statements. This is a hot code path in Jenkins, so any extra overhead here is a bit of a risk. The traditional best practice for this in Java is to guard such string concatenation with e.g. |
As @basil asked, here is another presumably not problematic subset of #59 that adds logging instrumentation in the code going through build parameter filtering. Due to the split of PRs, there may be a little formatting conflict vs. #75 that is another part of that original wad of code, and vs. subsequent PR with actual attempt at the fix.