Does AbortRun() still call EventAction::EndOfEventAction()?

[mkelsey]

This is a followup to a question of mine from 2021:

Does RunManager::AbortRun() work across all threads?

My application has the ability to read in event configurations from a text file, and process the resulting events. I’ve set up the reader with appropriate mutexes, so that each thread gets one complete event, and successive events get read in by the various worker threads. When the file reaches EOF, I have the code call G4RunManager::AbortRun(). This should end the run even if the user’s /run/beamOn had requested more events than the file contains. But that doesn’t seem to be happening. In …

I’m running G4 10.7.p04 for our experiment; if the behaviour I describe has changed in G4 11, please let me know.

When I call runManager->AbortRun(false) from a worker thread, my understanding is that this calls BroadcastAbortRun(false), which should (I think!) cause all of the worker threads to stop what they’re doing without completing the event they are on.

But when I look in my output file, I see events from all of the worker threads, including ones that were still in process when the AbortRun() call was made.

So my question is: when AbortRun() is sent to the worker threads, do they still call EventAction::EndOfEventAction() and RunAction::EndOfRunAction()? Or should the event loop on those workers simply be terminated?