-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Coverity fixes 82576, 82575, 68746, 68745, 68856, 61279, 61577 #526
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
Coverity fixes 82576, 82575, 68746, 68745, 68856, 61279, 61577 #526
Conversation
|
Starting build on |
|
Starting build on |
|
@phsft-bot build please. |
|
Starting build on |
|
Starting build on |
|
@phsft-bot build! |
|
Starting build on |
|
@phsft-bot build! |
|
Starting build on |
|
dbdff17 causes crash in stressHistogram. Do we understand why it was not seen/caught by the jenkins builds? |
|
Hmm... please feel free to revert this commit. Maybe @harveyj1953 knows what's going on there. |
|
@vgvassilev I am looking into the commit itself (which by the way had already been commit and reverted once). However my questions is really about jenkins. I.e. this failure is seen in the incremental builds (https://phsft-jenkins.cern.ch/job/root-incremental-master-noimt/BUILDTYPE=Debug,COMPILER=gcc49,LABEL=centos7/466/testReport/projectroot/test/test_stresshistogram/) ... and so my questions (to try to improve the process/infrastructure) is why it was not seen in the build made from the PR (i.e. is stressHistogram not run? did the build not finish? or something else?). thanks. |
|
@martinmine, do you have an idea? |
These are the missing items from #524.