Skip to content

WIP: Algorithm failing inside an event sub-slot causes segfault

Just a test-case so far. An algorithm scheduled inside a sub-slot and returning StatusCode::FAILURE can trigger a scheduler segfault if followed by another algorithm (but not otherwise).

Presumably a Gaudi-only demonstration of the issue described here: https://its.cern.ch/jira/browse/ATEAM-472

This MR created to allow sharing of the test code, and hopefully to become a solution in time.

Merge request reports