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

Adjust bounds for the memory stress test #1941

Closed
bbockelm opened this issue Jan 25, 2025 · 1 comment
Closed

Adjust bounds for the memory stress test #1941

bbockelm opened this issue Jan 25, 2025 · 1 comment
Assignees
@bbockelm
Labels
bug Something isn't working internal Internal code improvements, not user-facing test Improvements to the test suite

Comments

@bbockelm
Copy link
Collaborator

Since go is a garbage-collected language, the amount of memory it uses is not completely deterministic. The memory stress test repeats the same director operation over and over, looking for growth in memory -- within a given threshold.

That threshold seems to be too tight for the GitHub runner. Let's loosen it up to reduce failures.
@bbockelm bbockelm added bug Something isn't working internal Internal code improvements, not user-facing test Improvements to the test suite labels Jan 25, 2025
@bbockelm bbockelm self-assigned this Jan 25, 2025
@bbockelm bbockelm linked a pull request Jan 25, 2025 that will close this issue
Add more leeway to the stress test #1942
Closed
@brianaydemir
Copy link
Contributor

This issue was subsumed by #2027.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bbockelm bbockelm

Labels
bug Something isn't working internal Internal code improvements, not user-facing test Improvements to the test suite
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add more leeway to the stress test bbockelm/pelican
2 participants
@bbockelm @brianaydemir