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
Describe the bug
When pressing ctrl-C in various situations, parsl tends to hang. This is especially obvious to me in pytest, one of the main environments in which I run parsl code.
For example, pressing ctrl-C in a recent pytest run has left pytest waiting for parsl to shut down before exiting, while the parsl strategy code continues to attempt to launch (failing) blocks to run its one outstanding job on htex, apparently forever.
Other misbehaviour happens with monitoring - for example, see issue #2123 with LSST.
In general, parsl's handling of shutdown like this is pretty poor and needs a serious review and fixup to ensure that the various component processes can cope with being killed by means other than successful execution shutdown.
The text was updated successfully, but these errors were encountered:
The join parameter should never be set by a user, and gives bad error
messages if it is set - see issue #2174.
The parameter was only there so that the join_app decorator could be
implemented in terms of the python_app decorator. This PR changes how
that implementation works so that this misbehaviour is not exposed
to end users.
Fixes issue #2174
Describe the bug
When pressing ctrl-C in various situations, parsl tends to hang. This is especially obvious to me in
pytest
, one of the main environments in which I run parsl code.For example, pressing ctrl-C in a recent pytest run has left pytest waiting for parsl to shut down before exiting, while the parsl strategy code continues to attempt to launch (failing) blocks to run its one outstanding job on htex, apparently forever.
Other misbehaviour happens with monitoring - for example, see issue #2123 with LSST.
In general, parsl's handling of shutdown like this is pretty poor and needs a serious review and fixup to ensure that the various component processes can cope with being killed by means other than successful execution shutdown.
The text was updated successfully, but these errors were encountered: