-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Fix ordering bug in reworked PFBlockAlgo #14441
Conversation
@cmsbuild please test |
The tests are being triggered in jenkins. |
A new Pull Request was created by @lgray (Lindsey Gray) for CMSSW_8_1_X. It involves the following packages: RecoParticleFlow/PFProducer @cmsbuild, @cvuosalo, @slava77, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
+1
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar |
Hi Slava, can you point me to the information from valgrind? Thanks. |
I was running 1001.0 in CMSSW_8_1_X_2016-05-02-2300 (I suppose, it would be the same in pre4)
it's if( *pos != key || 0 == keys.size() ) { I don't see how keys.size can be uninitialized; so, it may be pos or key; but then I wasn't able to make sure of it with -O0 (valgrind crashes on code recompiled with -O0). So, given that it's after optimization, the line number may be misleading. It's unclear to me where it's coming upstream |
Ah, *pos may dereference keys.end(). This is fixed merely by changing the order of the clauses in the if statement. I can patch it up quickly right now if you're OK to resign? |
ok, please |
@cmsbuild please test |
The tests are being triggered in jenkins. |
Pull request #14441 was updated. @cmsbuild, @cvuosalo, @slava77, @davidlange6 can you please check and sign again. |
+1
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar |
+1 |
This ordering bug was causing crashes in relvals for 810pre4.
I have checked in a few cases that the exceptions are no longer thrown.
Notably, in these cases more blocks were being created than with the old algorithm.
With the bugfix provided here, the old behavior is restored.