-
Notifications
You must be signed in to change notification settings - Fork 60
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
2018 replay for PPS PCL test #4640
Conversation
run replay please |
Replay testing PR '2018 replay for PPS PCL test' |
There are 309 filesets not closed. |
There are 17 repack workflows. |
There are 15 repack workflows. |
There are 7 repack workflows. |
There are 7 repack workflows. |
Replay testing PR '2018 replay for PPS PCL test' |
There are 2971 filesets not closed. |
I'm closing this PR, with the comment that I made an issue here I'll reopen the PR in January when we have the 12_2_1 out. |
I'm reopening this, as the new CMSSW is expected to be out very soon |
Replay testing PR '2018 replay for PPS PCL test' |
There are 313 filesets not closed. |
Hi @jhonatanamado @GermanGiraldo I didnt actually mean to trigger tests yet, only in a few days when 12_2_1 is out. Please have them aborted. Thanks! |
There are 17 repack workflows. |
hi @tvami , thanks for let us know, we will fail all the workflows for this replay and as soon CMSSW_12_2_0_pre3 is ready you can trigger it again. |
New CMSSW is out, I'll submit a commit in a few minutes |
run replay please |
1 similar comment
run replay please |
Replay testing PR '2018 replay for PPS PCL test' |
There are 315 filesets not closed. |
There are 17 repack workflows. |
All jobs from StreamExpress workflow are paused due to the same issue
As can be seen, the issue is finding producers PPSTimingCalib' and 'PPSAlignment. Logs can be found here: |
@tamas After your fixes, we hit a similar error. Now the system is unable to find
|
@germanfgv ok I removed those, should we trigger tests again? |
All but one of the jobs were successful. The failing job is from workflow
The tarbal of the job can be found here:
|
Hi @germanfgv thanks for reporting this! |
Since the replay finished successfully for the PPS replay, I'm closing this PR! |
Hello I was wondering whether the error reported above by @germanfgv and commented by @francescobrivio is understood ? Thanks |
Hi, since this stream with the error was not the main goal of this replay and runs without any problems in other replays, we did not give it higher priority in investigating the failure. But we have just inquired with @germanfgv to learn which is producer that is raising the error so we can investigate it further. |
Replay Request
Requestor
AlCaDB
Describe the configuration
Release: ~~CMSSW_12_2_0_pre3 ~~ CMSSW_12_2_0_patch1
Run: 324841
GTs:
Additional changes:
Diffs in the GTs:
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/122X_dataRun3_Express_v1/122X_dataRun3_Express_TIER0_REPLAY_Run2_v1
and
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/122X_dataRun3_Prompt_v1/122X_dataRun3_Prompt_TIER0_REPLAY_Run2_v1
Removed the
PromptCalibProdSiPixel
since it's know to be an offender module, see https://hypernews.cern.ch/HyperNews/CMS/get/tier0-Ops/2325/1.htmlAdded PPS modules
promptCalibProdPPS
andPromptCalibProdPPSAlig
and PPS AlCaRECOsPPSCalTrackBasedSel
,PPSTimingCalib
, andPPSAlignment
Changed the settings to 2018
Purpose of the test
To test the newly introduced PPS PCL workflows. PPS data is not available in 2021, so we need to run on the 2018 data.
T0 Operations HyperNews thread
https://hypernews.cern.ch/HyperNews/CMS/get/tier0-Ops/2326.html