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
improvement of a workaround in customizeHLTforPatatrack
#36031
improvement of a workaround in customizeHLTforPatatrack
#36031
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36031/26486
|
A new Pull Request was created by @missirol (Marino Missiroli) for master. It involves the following packages:
@cmsbuild, @missirol, @Martin-Grunewald can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
enable gpu to test wfs that make use of |
please test with #36021 looks like this other unrelated PR is necessary to fix some of the PR tests |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-e8c569/20325/summary.html GPU Comparison SummarySummary:
Comparison SummaryThere are some workflows for which there are errors in the baseline: Summary:
|
+hlt
@qliphy @perrotta |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Recent changes in the HLT menu [*] (addition of a module in the path
AlCa_LumiPixelsCounts_Random_v1
; see CMSHLT-2189) have created a conflict between the12_2_X
GRun menu and a workaround used incustomizeHLTforPatatrack
.This PR fixes the issue with a small improvement to said workaround.
The final solution will be to fix the HLT path directly in
ConfDB
(this is being followed up in TSG; see CMSHLT-2195).FYI: @fwyzard
[*]
To be integrated in CMSSW in a separate PR later today.See #36034.PR validation:
Manual tests. Now the following works:
If this PR is a backport, please specify the original PR and why you need to backport that PR:
N/A