-
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
nano test scripts in CMSSW #39765
nano test scripts in CMSSW #39765
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39765/32628
|
A new Pull Request was created by @vlimant (vlimant) for master. It involves the following packages:
@cmsbuild, @swertz, @vlimant can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
thanks @vlimant , I will update bot to run these and include the results in PR summary. |
@vlimant , if |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39765/32636
|
@vlimant , looks like
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39765/32639 |
test parameters:
|
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-7c3bc5/28386/summary.html Comparison SummarySummary:
NANO Comparison Summary@slava77 comparisons for the following workflows were not done due to missing matrix map:
Summary:
Nano size comparison Summary:
|
+1 |
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, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
@vlimant @smuzaffar do I understand correctly that this PR can get merged even before cms-sw/cms-bot#1867 is finalized? (I see there are still ongoing discussions in it) |
yes @perrotta this PR can be merged. If we needed any changes then those will go in to cms-bot. |
from the scripts POV in this PR, things are final indeed. |
+1 |
PR description:
as discussed in #39452 the testing script for nano are being put in CMSSW to enable testing in PR integration
PR validation:
ran
`runTheMatrix.py --what nano -l 2500.601 --site "" --job-reports
./inspectNanoFile.py 2500.311_mc106Xul17v2+TTbarMINIAOD10.6_UL17v2+NANO_mc10.6ul17v2+HRV_NANO_mc/step2.root -j 2500.311-size.json
./inspectNanoFile.py 2500.601_mc126X+TTBarMINIAOD12.6+NANO_mc12.6+HRV_NANO_mc/step2.root -j 2500.601-size.json
./get_timing_from_jobreport.py 2500.311_mc106Xul17v2+TTbarMINIAOD10.6_UL17v2+NANO_mc10.6ul17v2+HRV_NANO_mc/JobReport2.xml 2500.311-timing.json
./get_timing_from_jobreport.py 2500.601_mc126X+TTBarMINIAOD12.6+NANO_mc12.6+HRV_NANO_mc/JobReport2.xml 2500.601-timing.json
./compare_sizes_json.py -H -f md 2500.601 2500.311 --ref "./" --base "{}-size.json,{}-timing.json" >> NANO_report.md`
to get a markdown print out that should be displayed in the summary.
N.B:
--ref
should point to a directory where we have reference files for comparison