Fix some compilation warnings when building StrippingCache and TurboCache

This will suppress some of the warnings when building both functors cache. However, the following type of warnings:

# WARNING: something else configured a decoder already, Raw/Spd/Digits CaloDigitsFromRaw/SpdFromRaw
# WARNING: file '/cvmfs/lhcbdev.cern.ch/nightlies/lhcb-2018-patches/479/DBASE/TCK/L0TCK/head/options/L0DUConfig.opts' already included, ignored.
# WARNING: Property 'DataType' is set in both 'DigiConf' and 'SimConf', using 'DigiConf.DataType'

won't be fixed because they are print (see https://gitlab.cern.ch/lhcb/LHCb/blob/2018-patches/DAQ/DAQSys/python/DAQSys/Configuration.py#L212) and not log.warning. The fixes here should suppress them if they are changed from print to log.warning in the corresponding other projects, if one aims for a clean DaVinci compilation.

If the latter is appropriate or worth to be done, I can do it, just let me know.

changed the description

• [2019-02-05 00:14] Validation started with lhcb-2018-patches#480

added 1 commit

• 9427d066 - Add FTAG known warning.

Compare with previous version

@erodrigu From having a look to the nightlies, this indeed suppressed quite a lot of known warnings (excepting those in the description).

OK, shall I go ahead and merge? Think so.

I'm tempted to propagate to run2-patches but not to master. Opinion?

I agree with you, master will need some dedicated fixes, what I was planning to do is to try to clean up master after these campaigns are done and anything relevant is merged there if needed. What do you think?

Perfect!

FYI I've just committed the reference update for the failing test of CommonParticles, see !287 (merged).

merged

mentioned in commit c2d758e5

mentioned in commit ee1e84d0

mentioned in merge request !288 (merged)