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
{{ message }}
This repository has been archived by the owner on Sep 7, 2018. It is now read-only.
When buster-ci is exited while tests are running, the agents (browser spawned process) is left open.
Subsequent execution of buster-ci is unaware of the agents. When buster-ci runs to the end and exits, the agents do not close and buster-ci exits the process with code 1.
I'm proposing that an exit event handler is attached to the buster-ci process to close agents if they remain open.
When
buster-ci
is exited while tests are running, the agents (browser spawned process) is left open.Subsequent execution of
buster-ci
is unaware of the agents. Whenbuster-ci
runs to the end and exits, the agents do not close andbuster-ci
exits the process with code 1.I'm proposing that an
exit
event handler is attached to thebuster-ci
process to close agents if they remain open.Some documentation on the process
exit
event: http://nodejs.org/api/process.html#process_event_exitThe text was updated successfully, but these errors were encountered: