LHCb merge requestshttps://gitlab.cern.ch/lhcb/LHCb/-/merge_requests2023-07-06T17:41:44+02:00https://gitlab.cern.ch/lhcb/LHCb/-/merge_requests/2984Draft: Decommission COOL2023-07-06T17:41:44+02:00Marco CattaneoDraft: Decommission COOLhttps://gitlab.cern.ch/lhcb/LHCb/-/merge_requests/4048Make sure Git resources are released before git_libgit2_shutdown (@clemenci)2024-03-28T00:22:01+01:00Marco CattaneoMake sure Git resources are released before git_libgit2_shutdown (@clemenci)It may happen (in some error condition) that finalize() is skipped, in
which case the Git resources might not be released before
~GitEntityResolver, so it's important to ensure they are released to
avoid a segfault.
Cherry-picked from !...It may happen (in some error condition) that finalize() is skipped, in
which case the Git resources might not be released before
~GitEntityResolver, so it's important to ensure they are released to
avoid a segfault.
Cherry-picked from !4032https://gitlab.cern.ch/lhcb/LHCb/-/merge_requests/4262Draft: Add test to check that we fail when condition version is missing2024-02-05T17:26:23+01:00Rosen MatevDraft: Add test to check that we fail when condition version is missing~~I noticed that jobs don't fail when the conditions version is a nonexistent tag/branch. This is quite bad. I'm not even sure what conditions are used in this case. ~~
Correction: I gave a nonexistent tag/branch but at the same time I ...~~I noticed that jobs don't fail when the conditions version is a nonexistent tag/branch. This is quite bad. I'm not even sure what conditions are used in this case. ~~
Correction: I gave a nonexistent tag/branch but at the same time I had `ConditionsLocation = 'file://...` which means the `ConditionsVersion` value is irrelevant. However, the INFO printout still suggests it is used, which is very misleading. On top of this, as far as I can see, there is no printout of the value of `ConditionsVersion`.
I would suggest that we abort in case `ConditionsVersion` is specified when `ConditionsLocation = 'file://...`.
OTOH, when we have `ConditionsLocation = 'git://...` and supply an nonexistent tag, the job fails but it does so very late. We need an early failure with a clear message.
Here I add a draft of a test for the expected behaviour.
Note that there were recent changes in https://gitlab.cern.ch/lhcb/Detector/-/merge_requests/422 which might have affected behaviour.
@sponce @bcouturi @clemencihttps://gitlab.cern.ch/lhcb/LHCb/-/merge_requests/4277PyConf: Add support for setting dd4hep.LimitedIOVPaths2024-03-21T18:06:04+01:00Christopher Rob Jonesjonesc@hep.phy.cam.ac.ukPyConf: Add support for setting dd4hep.LimitedIOVPathsPyConf: Add support for setting dd4hep.LimitedIOVPaths for conditions where a run-by-run entry is required in data
See lhcb/LHCb!4277
Requires lhcb/Panoptes!295PyConf: Add support for setting dd4hep.LimitedIOVPaths for conditions where a run-by-run entry is required in data
See lhcb/LHCb!4277
Requires lhcb/Panoptes!295