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.

Sign up for GitHub

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

Jump to bottom

[test] Check that memory leak when baseEnvironment.level > level is fixed #1152

Closed
LukasPietzschmann opened this issue Nov 17, 2024 · 0 comments · Fixed by #1171
Closed

[test] Check that memory leak when baseEnvironment.level > level is fixed #1152

LukasPietzschmann opened this issue Nov 17, 2024 · 0 comments · Fixed by #1171
Labels
test Relates to tests specifically

Comments

@LukasPietzschmann
Copy link
Collaborator

While commit 2380113 seems to have fixed the issue, there still needs to be tests to prevent future regressions.
@LukasPietzschmann LukasPietzschmann added the bug Something isn't working label Nov 17, 2024
@EagleoutIce EagleoutIce changed the title Memory leak when baseEnvironment.level > level [Test]: Check that memory leak when baseEnvironment.level > level is fixed Nov 18, 2024
@EagleoutIce EagleoutIce added test Relates to tests specifically and removed bug Something isn't working labels Nov 18, 2024
@EagleoutIce EagleoutIce changed the title [Test]: Check that memory leak when baseEnvironment.level > level is fixed [test] Check that memory leak when baseEnvironment.level > level is fixed Nov 23, 2024
@EagleoutIce EagleoutIce linked a pull request Nov 23, 2024 that will close this issue
test(inverted-caller): add new tests to trigger the previous problem #1171
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
test Relates to tests specifically
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

test(inverted-caller): add new tests to trigger the previous problem flowr-analysis/flowr
2 participants
@EagleoutIce @LukasPietzschmann