Skip to content
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

Logger continues after cleanup called #93

kylechard opened this Issue Feb 10, 2018 · 1 comment


None yet
2 participants
Copy link

kylechard commented Feb 10, 2018

Even after calling dfk.cleanup() the logger continues with log statements like the following:

2018-02-09 19:16:29,500 parsl.dataflow.strategy [DEBUG] Site:Local_Threads Status:STATIC


This comment has been minimized.

Copy link

yadudoc commented Feb 12, 2018

The timer thread used by strategy needs more logic to auto shutdown. I'm thinking this is an easy enhancement to release along with 0.5.0, but if we decide this is a bug we could potentially release this earlier (@kylechard ?)

@yadudoc yadudoc self-assigned this Feb 12, 2018

@yadudoc yadudoc added the enhancement label Feb 12, 2018

@yadudoc yadudoc added this to the Parsl-0.5.0 milestone Feb 14, 2018

@yadudoc yadudoc closed this in 678ce93 Feb 22, 2018

yadudoc added a commit that referenced this issue Feb 23, 2018

Bumping version from 0.4.0 to 0.4.1
Several fixes included as part of this point release:
* Cobalt provider issues with job state #101
* Parsl updates config inadvertently #98
* No blocks provisioned if parallelism/blocks = 0 #97
* Checkpoint restart assumes rundir bug #95
* Logger continues after cleanup called enhancement #93
* Error checkpointing when no cache enabled  #92
* Several fixes to libsubmit.

New Providers:
* GoogleCloud
* GridEngine
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
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.