Disable profiler in tests?
Open
diagnostics
feature
tests
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 778
- Avg merge
- 2h 50m
- Merged PRs (30d)
- 3
Description
We constantly have a profiler running in the background, often the threads associated to it are not properly cleaned up.
In https://github.com/dask/distributed/pull/6033 we discovered that it can also be responsible for holding on to references longer than necessary which should not be a problem in production but it is for testing.
On top of these and likely other problems, the profiler surely slows down our tests, particularly with converage enabled.
Should we not run the profiler at all for non-profiling related tests?
Contributor guide
Assessment
This issue has not been assessed yet.