-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
APE measurement tool: Resolved python3 compatibility issues, added unit test functionality, removed dependency on other package #42012
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42012/35973
|
A new Pull Request was created by @mteroerd (Marius Teroerde) for master. It involves the following packages:
@cmsbuild, @tvami, @saumyaphor4252, @francescobrivio can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
what about adding a unit test, to avoid this gets broken again in the future? |
I am not sure if it is worth the effort right now, since at some point this should get rewritten to something that uses dagman, in preparation of maybe including APE determination in the PCL. But if one were to add a unit test, one would also have to include the data skimming step if it's supposed to be a meaningful test. |
then please do, it should not be much effort! |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42012/35992
|
Pull request #42012 was updated. @cmsbuild, @tvami, @saumyaphor4252, @francescobrivio can you please check and sign again. |
@cmsbuild, please test |
-1 Failed Tests: UnitTests Unit TestsI found errors in the following unit tests: ---> test ApeTest had ERRORS Comparison SummarySummary:
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ccb048/33329/summary.html Comparison SummarySummary:
|
@cms-sw/alca-l2 please have a look. This needs to be backported. |
+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) |
+1 |
[13_1_X] APE measurement tool: Resolved python3 compatibility issues, added unit test functionality, removed dependency on other package: Backport of #42012
[13_0_X] APE measurement tool: Resolved python3 compatibility issues, added unit test functionality, removed dependency on other package: Backport of #42012
@mteroerd I notice that when running the APE unit tests in UBSAN IBs the following error message show up (see for example https://cmssdt.cern.ch/SDT/cgi-bin/logreader/el8_amd64_gcc11/CMSSW_13_2_UBSAN_X_2023-06-28-2300/unitTestLogs/Alignment/APEEstimation#/):
(etc.) Could you please have a look? |
By the way, the same also happens in the normal workflows, not only in tests (still for UBSAN builds): see e.g. wfs 136.843 , 140.066 , 140.107 , 158.5 @mmusich FYI |
Not clear what this has to do with the APE. Also from the log looks like a fwk problem to me. |
Yes, perhaps you are right @mmusich : I was misaddressed by seeing it first in the APE unit test added by this PR |
@cms-sw/core-l2 this is probably something you want to comment about |
Thank you @iarspider |
Not new - yes, not urgent - I would think so, nice to fix - definitely! |
PR description:
autoSubmitter.py did not run on recent CMSSW releases since ROOT does not work with python2, while python3 execution would throw an error from using the output of "check_output" without decode().
Some additional small changes to remove redundancies were applied, as well as a change to the disk space requested by condor jobs (the target input file size is 350MB, but files can be larger than 400MB anyway) and some formatting changes. Also, the method names now adhere to the CMS naming rules.
Additionally, added unit test functionality and removed the need to add the package Alignment/TrackerAlignment whenever a measurement is to be performed.
PR validation:
I executed the program with an example configuration and made sure it ran as expected. All changes should be transparent.
Also, a unit test can now be run to validate the PR.
If this PR will be backported please specify to which release cycle the backport is meant for:
Will be backported to 13_0_X and 13_1_X