Indeed WARNING messages are something that should be there in instances where user eyes are required. I would then advocate that examples and alike should ideally have none since they are meant to show best practices. In practice, I know that some of the warnings won't be trivial to get rid of quickly, especially that some come from code upstream. Still, it would be good to track them down and discuss with RTA in particular.
... at which point warnings truly become something to look at :-).
Edited
Designs
Child items
...
Linked items
0
Link issues together to show that they're related or that one is blocking others.
Learn more.
DaVinciExamples/python/DaVinciExamples/tupling/AllFunctors.py: ) # WARNING FunTupleBase<Gaudi::NamedRange_<std::vector<LHCb::Particle const*,std::allocator<LHCb::Particle const*> >,__gnu_cxx::__normal_iterator<LHCb::Particle const* const*,std::vector<LHCb::Particle const*,std::allocator<LHCb::Particle const*> > > > >:: Tuple 'DecayTree' 'unsigned long' has different sizes on 32/64 bit systems. Casting 'EVENTNUMBER' to 'unsigned long long'DaVinciExamples/python/DaVinciExamples/tupling/AllFunctors.py: ) # WARNING FunTupleBase<Gaudi::NamedRange_<std::vector<LHCb::Particle const*,std::allocator<LHCb::Particle const*> >,__gnu_cxx::__normal_iterator<LHCb::Particle const* const*,std::vector<LHCb::Particle const*,std::allocator<LHCb::Particle const*> > > > >:: Tuple 'DecayTree' 'unsigned long' has different sizes on 32/64 bit systems. Casting 'EVENTNUMBER' to 'unsigned long long'DaVinciExamples/tests/qmtest/tupling.qms/test_davinci_trigger_decisions.qmt:countErrorLines({"FATAL": 0, "WARNING": 0, "ERROR": 0},DaVinciExamples/tests/qmtest/tupling.qms/test_davinci_tupling_eventinfo.qmt:countErrorLines({"FATAL": 0, "WARNING": 0, "ERROR": 0},DaVinciExamples/tests/qmtest/tupling.qms/test_davinci_tupling_from_collections.qmt:countErrorLines({"FATAL": 0, "WARNING": 0, "ERROR": 0},DaVinciExamples/tests/qmtest/tupling.qms/test_davinci_tupling_mc_recinfo.qmt:countErrorLines({"FATAL": 0, "WARNING": 0, "ERROR": 0},DaVinciExamples/tests/refs/test_davinci_configFuntuple.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciExamples/tests/refs/test_davinci_configFuntuple.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciExamples/tests/refs/test_davinci_tupling-DTF-filtered.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciExamples/tests/refs/test_davinci_tupling-DTF-filtered.ref:Spruce WARNING HltDecReports has a zero TCK, and it is not explicitly specified for decoding -- make sure that this really what you wantDaVinciExamples/tests/refs/test_davinci_tupling-DTF-filtered.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciExamples/tests/refs/test_davinci_tupling-DTF-filtered.ref:Spruce WARNING HltDecReports has a zero TCK, and it is not explicitly specified for decoding -- make sure that this really what you wantDaVinciExamples/tests/refs/test_davinci_tupling-DTF-filtered.ref:Spruce WARNING HltDecReports has a zero TCK, and it is not explicitly specified for decoding -- make sure that this really what you wantDaVinciExamples/tests/refs/test_davinci_tupling-DTF-filtered.ref:Spruce WARNING HltDecReports has a zero TCK, and it is not explicitly specified for decoding -- make sure that this really what you wantDaVinciExamples/tests/refs/test_davinci_tupling-DTF-filtered.ref:Spruce WARNING HltDecReports has a zero TCK, and it is not explicitly specified for decoding -- make sure that this really what you wantDaVinciExamples/tests/refs/test_davinci_tupling-DTF-filtered.ref:Spruce WARNING HltDecReports has a zero TCK, and it is not explicitly specified for decoding -- make sure that this really what you wantDaVinciExamples/tests/refs/test_davinci_tupling-DTF-filtered.ref:Spruce WARNING HltDecReports has a zero TCK, and it is not explicitly specified for decoding -- make sure that this really what you wantDaVinciExamples/tests/refs/test_davinci_tupling-DTF-filtered.ref:Spruce WARNING HltDecReports has a zero TCK, and it is not explicitly specified for decoding -- make sure that this really what you wantDaVinciExamples/tests/refs/test_davinci_tupling-DTF-filtered.ref:Spruce WARNING HltDecReports has a zero TCK, and it is not explicitly specified for decoding -- make sure that this really what you wantDaVinciExamples/tests/refs/test_davinci_tupling-DTF-filtered.ref:Spruce WARNING Suppressing message: ' HltDecReports has a zero TCK, and it is not explicitly specified for decoding -- make sure that this really what you want'DaVinciExamples/tests/refs/test_davinci_tupling_array_taggers.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciExamples/tests/refs/test_davinci_tupling_array_taggers.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciExamples/tests/refs/test_davinci_tupling_eventinfo.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciExamples/tests/refs/test_davinci_tupling_eventinfo.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciExamples/tests/refs/test_davinci_tupling_from_passthrough.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciExamples/tests/refs/test_davinci_tupling_from_passthrough.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciExamples/tests/refs/test_davinci_tupling_from_spruce.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciExamples/tests/refs/test_davinci_tupling_from_spruce.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciExamples/tests/refs/test_davinci_tupling_weightedrelation_trackvariables.ref:HiveDataBrokerSvc WARNING non-reentrant algorithm: RecordStream/FSROutputStreamDstWriterDaVinciExamples/tests/refs/test_davinci_tupling_weightedrelation_trackvariables.ref:Hlt2 WARNING TCK obtained from rawbank seems to be 0 -- blindly ASSUMING that the current HltANNSvc somehow has the same configuration as when the input data was written. Proceed at your own risk, good luck...DaVinciTests/python/DaVinciTests/QMTest/DaVinciExclusions.py: "ToolSvc.TrackStateProvider.Track... WARNING TransportSvc is currently incompatible with DD4HEP .*",DaVinciTests/python/DaVinciTests/QMTest/DaVinciExclusions.py: "ToolSvc.TrackStateProvider.Track... WARNING See https://gitlab.cern.ch/lhcb/Rec/-/issues/326 for more details",DaVinciTests/python/DaVinciTests/QMTest/DaVinciExclusions.py: # expected WARNINGs from the data brokerDaVinciTests/python/DaVinciTests/QMTest/DaVinciExclusions.py: r"HiveDataBrokerSvc +WARNING non-reentrant algorithm: .*",DaVinciTests/python/DaVinciTests/QMTest/DaVinciExclusions.py: r"HltPackedBufferDecoder +WARNING TCK in rawbank seems to be 0 .*",DaVinciTests/python/DaVinciTests/QMTest/DaVinciExclusions.py: r"HltPackedBufferDe...WARNING TCK in rawbank seems to be 0 .*",DaVinciTests/python/DaVinciTests/QMTest/DaVinciExclusions.py: r"HltDecReportsDecoder +WARNING TCK obtained from rawbank seems to be 0 .*",DaVinciTests/python/DaVinciTests/QMTest/DaVinciExclusions.py: r"Hlt. +WARNING TCK obtained from rawbank seems to be 0 .*",DaVinciTests/python/DaVinciTests/QMTest/DaVinciExclusions.py: r"Hlt2DecReports +WARNING TCK obtained from rawbank seems to be 0 .*",DaVinciTests/python/DaVinciTests/QMTest/DaVinciExclusions.py: r"SpruceDecReports +WARNING TCK obtained from rawbank seems to be 0 .*",DaVinciTests/python/DaVinciTests/QMTest/DaVinciExclusions.py: r"Spruce +WARNING TCK obtained from rawbank seems to be 0 .*",DaVinciTests/python/DaVinciTests/QMTest/DaVinciExclusions.py: "WARNING: MC tools not functional yet outside Hlt2 - .*",DaVinciTests/python/DaVinciTests/QMTest/DaVinciExclusions.py: r"[a-zA-Z0-9]* +WARNING FunTupleBase<KeyedContainer<LHCb::MCParticle,Containers::KeyedObjectManager<Containers::hashmap> > >:: .*",DaVinciTests/python/DaVinciTests/QMTest/DaVinciExclusions.py: r"[a-zA-Z0-9]* +WARNING TransportSvc is currently incompatible with DD4HEP. .*",DaVinciTests/python/DaVinciTests/QMTest/DaVinciExclusions.py: r"[a-zA-Z0-9]* +WARNING See https://gitlab.cern.ch/lhcb/Rec/-/issues/326 for more details",DaVinciTests/tests/refs/test_davinci_filters.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciTests/tests/refs/test_davinci_funtuple_array.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciTests/tests/refs/test_davinci_funtuple_array.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciTests/tests/refs/test_davinci_recVertices.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciTests/tests/refs/test_davinci_recVertices.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciTutorials/README.md:Alternatively, if you need to make non-trivial changes build your own [stack](https://gitlab.cern.ch/rmatev/lb-stack-setup) for DaVinci (WARNING: Takes a very long time to build and is not suited to virtual machines like lxplus)DaVinciTutorials/tests/refs/test_tutorial0_basic_DVjob.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciTutorials/tests/refs/test_tutorial0_basic_DVjob.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciTutorials/tests/refs/test_tutorial1_Functors_specialfield.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciTutorials/tests/refs/test_tutorial1_Functors_specialfield.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciTutorials/tests/refs/test_tutorial2_LoKi.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciTutorials/tests/refs/test_tutorial2_LoKi.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciTutorials/tests/refs/test_tutorial3_ThOrfunctors.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciTutorials/tests/refs/test_tutorial3_ThOrfunctors.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciTutorials/tests/refs/test_tutorial4_trigger_eventinfo.ref:HiveDataBrokerSvc WARNING non-reentrant algorithm: RecordStream/FSROutputStreamDstWriterDaVinciTutorials/tests/refs/test_tutorial4_trigger_eventinfo.ref:HLT2 WARNING TCK obtained from rawbank seems to be 0 -- blindly ASSUMING that the current HltANNSvc somehow has the same configuration as when the input data was written. Proceed at your own risk, good luck...DaVinciTutorials/tests/refs/test_tutorial5_MCTruth.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciTutorials/tests/refs/test_tutorial5_MCTruth.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciTutorials/tests/refs/test_tutorial6_DecayTreeFit.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciTutorials/tests/refs/test_tutorial6_DecayTreeFit.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciTutorials/tests/refs/test_tutorial7_multiple_sel_lines.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...DaVinciTutorials/tests/refs/test_tutorial7_multiple_sel_lines.ref:HltANNSvc WARNING key 0x######## has an explicitly configured overrule -- using that...
I need to look at the WARNINGs we exclude. We don't see them in tests but they are there.
There are plenty of WARNING HltDecReports has a zero TCK, and it is not explicitly specified for decoding -- make sure that this really what you want. Does this need to be a warning?
Same for WARNING key 0x######## has an explicitly configured overrule -- using that...
The most scary is WARNING TCK obtained from rawbank seems to be 0 -- blindly ASSUMING that the current HltANNSvc somehow has the same configuration as when the input data was written. Proceed at your own risk, good luck...
2 & 4 should never happen with data produced after summer 2022...
3 should never happen for 'production running' (where keys should be present in the file-content-metadata repository), but may happen for 'standalone' user productions which may want to avoid 'polluting' the central file-content-metadata repository. Hence it is a very valid WARNING, as if the person knows what they are doing, and they are doing this on purpose it is OK, but if they don't then it may result in useless data...