You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a job is cancelled, SelFIe will not log anything when the process is killed.
It is possible to intercept the stop signals (int term quit) and print stats (& remember it's been printed to avoid duplicates if handled properly?) then propagate (get existing handler, handle, call next one; if no next one unregister oneself and send again maybe? would need to check that part) so one could get logs on jobs being cancelled, unless they're stuck in IO or something until sigkill finally comes.
The text was updated successfully, but these errors were encountered:
If a job is cancelled, SelFIe will not log anything when the process is killed.
It is possible to intercept the stop signals (int term quit) and print stats (& remember it's been printed to avoid duplicates if handled properly?) then propagate (get existing handler, handle, call next one; if no next one unregister oneself and send again maybe? would need to check that part) so one could get logs on jobs being cancelled, unless they're stuck in IO or something until sigkill finally comes.
The text was updated successfully, but these errors were encountered: