it avoids spurious test failures on busy Gitlab-CI runners

add support for multiple CF parents to topological execution flow tracer, and verbose/error messages cleanup in PRG

Gitlab CI authored 6 years ago and Hadrien Benjamin Grasland committed 6 years ago

patch generated by https://gitlab.cern.ch/hgraslan/Gaudi/-/jobs/1253552

https://coverity.cern.ch/reports.htm#v13572/p10041/fileInstanceId=763879735&defectInstanceId=396360581&mergedDefectId=98201

Change

operator<<( std::ostream& s, AlgsExecutionStates::State x )

to convert to string instead of integer. The latter was nowhere used.
Use the operator in EntityState to avoid the duplicate enum-to-string
hard-coding.

- require public constructor for components
- removed XyzFactory classes
- enabled warning for XyzFactory headers
- some clean up and modernization

Use std::map instead of std::unordered_map for algosDependenciesMap,
so that the output will be printed in a well-defined order.

ToolHandle is not thread-safe.
In order to be able to run thread initialization in parallel,
we need to make thread-local copies of the ToolHandleArray.

Needed to allow running part of the G4 initialization in parallel
for the ATLAS simulation.  Makes a significant difference  on many-core
machines like KNL.

see #15

The StatusCode now consists of a value and category/domain. By default
StatusCodes are created within a "default category". But users can
define new categories and StatusCodes using typed enums. The design is
mainly borrowed from std::error_code.

Main changes:
- StatusCode::setCode has been removed
- No implicit conversions from/to bool or int anymore. This greatly
  increases type safety.
- Converted all unscoped enums in Gaudi to their own StatusCode
  category (Clients will have to adjust their code to the scoped enum
  names (e.g. ERR -> Status::ERR)
- Added operator bool() that is equivalent to isSuccess()
- Added ternary (bitwise) AND(&) and OR(|) operators to combine
  StatusCodes according to three-valued logic
- Added extensive unit tests for all StatusCode features

Impact on clients:
- Code that relies on the implicit StatusCode<->bool/int conversion has
  to be changed to explicitly construct/convert StatusCodes via either
  the constructor, operator bool() or getCode().
- Clients using Gaudi StatusCodes need to adjust to using the scoped
  enums. E.g. clients of the ConversionSvc need to change BAD_STORAGE_TYPE to
  Status::BAD_STORAGE_TYPE when checking for specific StatusCode return
  types.

add TimelineSvc-based implementation of 'last running schedule' detection (used in scheduler state dumps)

Algorithms should not know about begin and end run transitions,
as these concepts become fuzzy if not entirely meaningless in
an environment where multiple events are processed concurrently.
In the vast majority of cases, anything done in
Algorithm::beginRun can be migrated to Algorithm::start, and
endRun -> stop.