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
Turn-off GEM-CSC integrated local trigger in valCscStage2Digis [11_3_X] #33679
Turn-off GEM-CSC integrated local trigger in valCscStage2Digis [11_3_X] #33679
Conversation
A new Pull Request was created by @dildick (Sven Dildick) for CMSSW_11_3_X. It involves the following packages: DQM/L1TMonitor @andrius-k, @kmaeshima, @ErnestaP, @ahmad3213, @cmsbuild, @jfernan2, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
urgent |
I can confirm that this PR solves the problem. Here's the print-out from the test
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-7081cf/14967/summary.html Comparison SummarySummary:
|
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_11_3_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_0_X is complete. This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
hi- does anyone understand why this issue did not come up during relvals? |
When we were testing the 11_2_X version and 11_3_X version, they passed all normal integration tests. However, the 11_2_X version crashed at P5. 11_3_X was not tested at P5 then. I turned off the GEM-CSC trigger in 11_2_X, but did not do that in 11_3_X. That should have been done in 11_3_X as well. |
Is this code not run anywhere outside of p5 and Tier0? (Eg, is there no unit test or relval that exercises it?)
… On May 11, 2021, at 2:20 PM, Sven Dildick ***@***.***> wrote:
When we were testing the 11_2_X version and 11_3_X version, they passed all normal integration tests. However, the 11_2_X version crashed at P5. 11_3_X was not tested at P5 then. I turned off the GEM-CSC trigger in 11_2_X, but did not do that in 11_3_X. That should have been done in 11_3_X as well.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
The code should be run on data to check data-emulator agreements for the CSC local trigger. A few weeks ago they must have switched from running 11_2_X to 11_3_X at P5. |
So “no”.
Its best practice to ensure that things run in some relval -eg the data run3 relval - so that problems don’t get missed until production starts..Maybe its good if you can see if/why those relvals don’t fit your use case and open an issue to fix that.
… On May 11, 2021, at 2:27 PM, Sven Dildick ***@***.***> wrote:
The code should be run on data to check data-emulator agreements for the CSC local trigger. A few weeks ago they must have switched from running 11_2_X to 11_3_X at P5.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@davidlange6 @amassiro @boudoul you can easily reproduce the error by cherry-picking the crashing event and using step1 of
I'm trying to run on The command used in RelVals is @germanfgv do you know how many events ran successfully in the replay test dmwm/T0#4572 before the crash? |
@dildick there is an error in the Express (it should be 11_2_4) Can it be related to this PR? (I mean that this PR would solve this crash) cc @cms-sw/l1-l2 @cms-sw/dqm-l2 |
@eyigitba This is a crash in |
@silviodonato honestly, I'm not sure where to look for that information, but we still have logs and PSet for those jobs. So maybe we can find out if you point me into the right direction. |
@dildick @silviodonato I am aware of that crash. It's in the EMTF unpacker part which was not being used until now. I can submit a PR tomorrow to fix it. |
PR description:
Turn-off GEM-CSC integrated local trigger in valCscStage2Digis. GEM-CSC trigger is not yet deployed at P5. Previously it was turned off in 11_2_X.
PR validation:
Tested with WF 11634.0.
Also tested this on a data event (341169:517:9310078) that was crashing the T0-replay. This recipe, which crashed before, should now run:
if this PR is a backport please specify the original PR and why you need to backport that PR:
Backport of #33678
Before submitting your pull requests, make sure you followed this checklist: