-
-
Notifications
You must be signed in to change notification settings - Fork 727
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
Disable profiler in tests? #6075
Labels
Comments
I think that we should not run the profiler during non-profiling tests.
…On Wed, Apr 6, 2022 at 3:54 AM Florian Jetter ***@***.***> wrote:
We constantly have a profiler running in the background, often the threads
associated to it are not properly cleaned up.
In #6033 <#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?
—
Reply to this email directly, view it on GitHub
<#6075>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACKZTFPKZSVXK6RY3JA2RLVDVGLDANCNFSM5SVJUQZQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
see also #4091 |
See also #6421 |
My proposed course of action is
Nice to have
|
2 tasks
we missed a few tests that start the profiler by accident see #6498 |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
We constantly have a profiler running in the background, often the threads associated to it are not properly cleaned up.
In #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?
The text was updated successfully, but these errors were encountered: