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
Under some conditions the job program might exit, such as if it has decided it has reached a fatal condition or hit a self-imposed timeout. Unfortunately, the child process exiting is not presently enough to end the buildomat job; I believe we will also wait to read everything we can read from the stdout and stderr descriptors, which may be shared with and then held open by background processes.
When the child process exits, we should start a timer (say, 30-60 seconds) and abandon the file descriptors at that point even if we have not hit EOF. This condition should at least result in a warning message in the job event stream, and probably also fail the job.
The text was updated successfully, but these errors were encountered:
I decided not to make it an error for now, just a warning. We'll wait ~5 seconds for the descriptors to drain once the child process exits, in an attempt to print any remaining output prior to rendering the exit status. Then, if the descriptors were not closed after that delay we'll report a warning to let the user know we're waiting another 60 seconds. If the descriptors are still not closed, we report which (stderr or stdout or both) are still open and end the task. File uploads will then happen as normal, etc.
This was implemented in 94e05c4, which has now been deployed as well.
Under some conditions the job program might exit, such as if it has decided it has reached a fatal condition or hit a self-imposed timeout. Unfortunately, the child process exiting is not presently enough to end the buildomat job; I believe we will also wait to read everything we can read from the
stdout
andstderr
descriptors, which may be shared with and then held open by background processes.When the child process exits, we should start a timer (say, 30-60 seconds) and abandon the file descriptors at that point even if we have not hit EOF. This condition should at least result in a warning message in the job event stream, and probably also fail the job.
The text was updated successfully, but these errors were encountered: