Made sure that xAOD::TEvent in CP::xAODWriterAlg would not become the "active" event.
In certain situations it was possible to end up with the member object of this algorithm becoming the "active event" of the job. Which would lead to all sorts of problems in the dual-use tools of the job. Former-commit-id: 67226ad74aeb4b163d18aec199035f98234e3a74
Showing with 4 additions and 0 deletions