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.

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

Added sleep in dataframe_memory_leak test after gc collection #494

Merged
merged 2 commits into from
Feb 4, 2025

Conversation

tomuben
Copy link
Collaborator

@tomuben tomuben commented Jan 30, 2025

related to exasol/script-languages-release#1060

We suspect that GC is not finished when the test reads the memory snapshot => Sleep 1s after triggerer GC might fix this problem.
I ran the AWS Build with exasol/script-languages-release#1061 3x and it worked. So the workaround looks promising.

@@ -111,6 +112,7 @@ def run(ctx):
assert memory_check_executed == False #Sanity check for row number
print("Checking memory usage", flush=True)
gc.collect()
time.sleep(1)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In case it works we should a comment to the sleeps

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.
The CI Build failed because of Docker.

@tomuben tomuben merged commit 9f97d1d into master Feb 4, 2025
25 checks passed
@tomuben tomuben deleted the bug/1060_analyze_memory_leakage_test_failures branch February 4, 2025 11:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants