see https://sft.its.cern.ch/jira/browse/ROOT-10872?focusedCommentId=109891&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-109891

See merge request !1121

See merge request !1122

See merge request !1126

See merge request !1124

See merge request !1091

Do not print default value of `DataHandle` if its value is unchange from
the default.

- add support for `isCondition` flag
- add mode, type and isCondition values to option representation
- make `setstate`/`getstate` generic
- improve unit test coverage

Support derived classes of `DataHandleProperty`. Requires passing the
actual type of the DataHandle and extending `genconf` to be able to
detect derived classes.

Change the handle member to `protected` so it can be re-used in derived
classes.

Move the property declaration of data handles one level lower in the
inheritance hierarchy, i.e. from `DataObjectHandleBase` to `DataHandle`. The
only user-visible change should be the change in type of the python
configurable class from `DataObjectHandleBase` to `DataHandle`. This change
will allow other types of handles (e.g. in ATLAS) to profit from the
python type information.

Add accessor for the class name of `DataObjID` (for the ATLAS case).
This avoids having to parse the result of `fullKey()`.

update units and constants

See merge request !1101

Avoid output file conflict in MetaDataSvc test

See merge request !1123

See merge request !1120

See merge request !1104

See merge request !1090

See merge request !1086

See merge request gaudi/Gaudi!1088

Revert "Revert "Merge branch 'SubSlotExceptions' into 'master'""

See merge request !1107

Benjamin Michael Wynne authored 4 years ago and Marco Clemencic committed 4 years ago

This reverts commit 0f268e1f.

Check build warnings in GitLab CI

See merge request !1109

See merge request !1114

Explicitly flush cout in MessageSvc::finalize()

See merge request !1117

After switching to python3 in Athena, we started to see intermittent garbled
output coming from MessageSvc::finalize() and from terminate() of the AppMgr.
Apparently the output flushing somehow behaves differently in the print function
of python3 vs python2, that's why the problem had not been spotted before.
Explicit flushing of cout inside MessageSvc::finalize() is expected to fix
this problem.

the warnings are referring to the wrong versions and confusing

Add a new set of jobs `build-check:...` that would pass if there are no
warnings and would "fail" otherwise. Since the job is allowed to fail,
the failure would be reflected as a yellow job/pipeline status.

See merge request !1105

See merge request !1111