Issue 629: Memory management #809
Conversation
|
@treiher There are two non-covered lines currently, I would like some guidance on how to get rid of them. |
|
@treiher Also, how to deal with the "test_spark" tests? They can't use the allocator, can they? Maybe the proper fix is to not delete the |
These tests are only testing messages (not sessions), so I don't see how the allocator could be used there. Are there reasons against keeping the |
Yes, I will put the |
kanigsson
force-pushed
the
issue_629
branch
3 times, most recently
from
28c7b75
to
5cb01ab
Compare
kanigsson
force-pushed
the
issue_629
branch
7 times, most recently
from
e295154
to
2b7d603
Compare
|
@kanigsson Could you please change your commits so that the update of the session and shape files is done only once in the last commit? Loading the "Files changed" page with this huge amount of changes takes very long and the many files make it hard to see the actual changes. GitHub unfortunately changed the file filter again and all files are listed even when filtered out, which doesn't help much. |
script now skips the __pycache__ folder if present.
* more explicit argument "off" for SparkMode * assertion instead of "fail" * no need for allocator enum in subsystem class
No description provided.