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
Currently limit_memory will count the allocations made in other threads (if I understood it right). I want an option to count only the memory allocations made on the current thread (the thread running the test code).
you can create the server in a thread in the test setup
but you don't want to track the memory consumption in the "server" only in the SUT (the network library).
Related to #109 (comment) , In this case there are threads started for some tests that are never terminated, the allocations from those unrelated threads show as part of limit_memory on a later test. Ideally although those threads should have been terminated they should not show up in the later test.
The alternatives is to run the server outside the test framework, or use multiprocessing, both alternatives since they run the server in a different process won't show up in the limit_memory but that requires other means to control the server. When having the server as a thread you can have more tight control/communication so it's convenient.
The text was updated successfully, but these errors were encountered:
Feature Request
Currently
limit_memory
will count the allocations made in other threads (if I understood it right). I want an option to count only the memory allocations made on the current thread (the thread running the test code).The use case is
Related to #109 (comment) , In this case there are threads started for some tests that are never terminated, the allocations from those unrelated threads show as part of limit_memory on a later test. Ideally although those threads should have been terminated they should not show up in the later test.
The alternatives is to run the server outside the test framework, or use
multiprocessing
, both alternatives since they run the server in a different process won't show up in thelimit_memory
but that requires other means to control the server. When having the server as a thread you can have more tight control/communication so it's convenient.The text was updated successfully, but these errors were encountered: