-
-
Notifications
You must be signed in to change notification settings - Fork 720
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
Mock process memory readings in test_worker.py (v2) #5878
Merged
Merged
Changes from all commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
19d8bef
Fix flaky test_spill_hysteresis
crusaderky 8f2ffa2
stress test
crusaderky bddd7c3
xfail
crusaderky df14e24
test resilience
crusaderky ad8803e
redesign with nannies
crusaderky 34a790a
Stress test
crusaderky cb1f369
xfail on MacOS
crusaderky ab561c2
don't saturate dask org CI
crusaderky ef0e44b
improve resilience of test_pause_executor
crusaderky e484378
Revert "improve resilience of test_pause_executor"
crusaderky 24742b2
Merge branch 'main' into spill_hysteresis
crusaderky 8152265
Revert stress test
crusaderky 119ffa4
Merge branch 'main' into spill_hysteresis2
crusaderky cce8513
mock_rss
crusaderky deca19b
test_worker.py
crusaderky 3e56328
Merge branch 'main' into spill_hysteresis2
crusaderky 73d856a
Merge branch 'main' into spill_hysteresis3
crusaderky 8d89957
Third time's the charmer
crusaderky 1c257e3
Move to SystemMonitor
crusaderky 3484f0c
cleanup
crusaderky File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bit fragile. As soon as the while loop in the memory monitor changes anything about how it awaits, e.g. another async call to evict data, this condition will break since we rely on skipping exactly one loop iteration with
sleep(0)
.I can't come up with a nicer way other than sleeping for a longer time so this is fine for me. I just wanted to raise this in case somebody else thinks of something
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another ugly thing we can do but I think I dislike this even more is to wait for
_memory_monitoring
to toggle since then we know for sure thememory_monitor
is done. I think I prefer sticking with sleep(0) and deal with a test failure/test rewrite if that ever happens