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
recoConversion comparison instability in WF 23234.0 #32338
Comments
assign reconstruction,upgrade |
A new Issue was created by @kpedro88 Kevin Pedro. @Dr15Jones, @dpiparo, @silviodonato, @smuzaffar, @makortel, @qliphy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
The PR tests you quote use CMSSW_11_3_X_2020-11-29-0000, right? Would that mean that the effects of all PRs merged since then would show up in the comparisons I'm just worried that this issue might be related to my PR #32266 that indeed touched the conversion producer code, and this PR was one of two that was merged since the release that was used for the comparison baseline I think: https://cmssdt.cern.ch/SDT/html/showIB.html However, #32266 only moved code from some |
Usually, the bot posts a notification if it merges additional PRs on top of the IB. I don't see that in this case. |
No, only the PRs merged before CMSSW_11_3_X_2020-11-29-0000 can be responsible. Your own was only merged later on in CMSSW_11_3_X_2020-11-29-2300 |
is there any indication of the problem before CMSSW_11_3_X_2020-11-29-0000? |
I hadn't noticed the problem before today (but was offline for the holiday the past few days). The gcc version change is worth checking. |
@kpedro88 , is this still an open issue? |
@smuzaffar can you fix the bot so it stops removing my labels? I don't recall observing these spurious differences recently, but I'm also not aware of a particular PR that would have fixed them. Current L2s are probably more attentive to this than I am. |
This happened again in #36910 for 12_1_X, ZMM13TeV2017wf10042p0. |
Spurious differences in recoConversion quantities have started appearing in WF 23234.0 (2026 D49):
Observed in the following PR tests so far:
#32324
#32326
#32327
The text was updated successfully, but these errors were encountered: