-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running over more events than present or all events (using -1
) should exit with 0
#125
Labels
enhancement
New feature or request
Comments
This was referenced Jul 20, 2023
Closed
Zehvogel
added a commit
to Zehvogel/k4FWCore
that referenced
this issue
Aug 2, 2023
… `-1`) should exit with 0 key4hep#125
Zehvogel
added a commit
to Zehvogel/k4FWCore
that referenced
this issue
Aug 3, 2023
… `-1`) should exit with 0 key4hep#125
Zehvogel
added a commit
to Zehvogel/k4FWCore
that referenced
this issue
Aug 3, 2023
… `-1`) should exit with 0 key4hep#125
Zehvogel
added a commit
to Zehvogel/k4FWCore
that referenced
this issue
Aug 11, 2023
… `-1`) should exit with 0 key4hep#125
Zehvogel
added a commit
to Zehvogel/k4FWCore
that referenced
this issue
Aug 22, 2023
… `-1`) should exit with 0 key4hep#125
Zehvogel
added a commit
to Zehvogel/k4FWCore
that referenced
this issue
Aug 22, 2023
… `-1`) should exit with 0 key4hep#125
Zehvogel
added a commit
to Zehvogel/k4FWCore
that referenced
this issue
Aug 23, 2023
… `-1`) should exit with 0 key4hep#125
Zehvogel
added a commit
to Zehvogel/k4FWCore
that referenced
this issue
Sep 1, 2023
… `-1`) should exit with 0 key4hep#125
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently anything that makes Gaudi use a
IEventProcessor::stopRun
makes the whole process exit with exit code 4 (see here).This requires us to do things like this in tests:
k4FWCore/test/k4FWCoreTest/CMakeLists.txt
Lines 60 to 62 in 33ba587
It also makes it impossible to defensively script (using
-e
). This should be fixed somehow, although I do not know how.The text was updated successfully, but these errors were encountered: