Some additions to the conddb command line interface #32795
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32795/20969
|
|
A new Pull Request was created by @mmusich (Marco Musich) for master. It involves the following packages: CondCore/Utilities @ggovi, @cmsbuild can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
@cmsbuild please test |
mmusich
changed the title
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-1b630f/12657/summary.html Comparison SummarySummary:
|
mmusich
force-pushed
the
conddb_cli_update
branch
from
6b7fa1b to
70634ba
Compare
cmsbuild
added
code-checks-pending
tests-pending
and removed
code-checks-approved
tests-approved
labels
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32795/20971
|
|
@cmsbuild, please test |
|
please test |
|
@mmusich To avoid conflicts, I guess I should wait for this PR to be merged before to issue my PR ( with the listRun changes )? |
|
@ggovi as you prefer. I can rebase after yours or you can wait for this to be merged. |
|
@mmusich Let's go ahead with this one since we are here! Mine will follow right after... |
|
-1 Failed Tests: RelVals RelVals-INPUT AddOn RelValsExpand to see more relval errors ...RelVals-INPUT
Expand to see more relval errors ...
AddOn TestsExpand to see more addon errors ... |
|
@smuzaffar is there already an IB suitable for testing without spurious errors? |
|
we now have the new IB where you should not see these massive errors but we still get random crashes ( see #32796 ) |
|
@cmsbuild, please test |
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-1b630f/12690/summary.html Comparison SummarySummary:
|
|
+1 |
cmsbuild
added
db-approved
fully-signed
and removed
db-pending
pending-signatures
labels
|
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. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
|
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR description:
The purpose of this PR is to add few useful functionalities to the
conddbcommand line interface I used over the years and IMHO are missing from the current tool.They used to live as separate scripts in this repo (https://github.com/cms-AlCaDB/AlCaTools), but I think it would be more beneficial to distribute them via
cmsswfor wider usage.Two new commands are added:
conddb listParentTags: allows to list all tags that contain a given payload hash. Takes the payload hash as argument;conddb diffGlobalTagsAtRun: allows to compile the difference in terms of payloads for a pair of Global Tags, but comparing it at a given run-number (so eliminating all the spurious difference due to different tag names, but having actual same palyoads on a given IoV, etc.). This in my opinion is particularly useful when performing release validation and / or data certification, because the end-user - very frequently -would like to know what are the differences in terms of conditions between two Global Tags in data, but only for the run which is currently under examination.PR validation:
After compiling and
env-ing the environment, I've run successfully the new commands, e.g.:if this PR is a backport please specify the original PR and why you need to backport that PR:
Not a backport, no backport needed.
I am tagging also AlCa conveners as these tools might (or might not) be useful in their everyday work (especially when compiling differences of Global Tags for Relvals for PdmV):
cc:
@christopheralanwest @tlampen @francescobrivio