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
Minor enhancements to special geometry comparison test #29278
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29278/14333
|
A new Pull Request was created by @cvuosalo (Carl Vuosalo) for master. It involves the following packages: CondTools/Geometry @andrius-k, @Dr15Jones, @makortel, @cvuosalo, @schneiml, @ianna, @mdhildreth, @cmsbuild, @kmaeshima, @jfernan2, @fioriNTU, @civanch, @ggovi can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@ggovi Please check |
@cmsbuild please test |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
+1 |
+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. @davidlange6, @silviodonato, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
runDDDvsDBGeometryValidation.sh
is a special test to be run by experts to compare the geometry in a local database and the Conditions database. One test in the script is to compare the concatenated geometry XML files in each database. These files may actually differ, or they may only appear to differ because of different ordering of some of the content of the files.I added a two more tests to the script to try to help the expert determine whether there are real differences in the two geometry XML files or whether the apparent differences are due to minor re-ordering. The overall problem of definitively determining whether two big XML files are functionally identical even if their parts are in different orders is still not solved, though the enhancements in this PR are a step in that direction. Maybe this issue can be fully resolved in a later PR.
One file in this PR is unrelated to the others.
splitExtended2021Database.sh
is used for creating payloads. The DB group requested that I update the command used in the script fromconddb_import
, which is intended to be decommissioned, toconddb
.PR validation:
The scripts run and produce informative output. They have no effect on production workflows or unit tests.
splitExtended2021Database.sh
continues to work and create payloads. With the change in command, I noticed that the comment field in the payload changed. For example, the oldconddb_import
created the following payload. Note the Description field.The new
conddb
created almost the same payload:Note that Description field is different. I assume this difference is harmless.
No backport is needed for this PR.