-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
[core][oom] Use retriable lifo policy for dask 3x nightly test #32361
Conversation
Signed-off-by: Clarence Ng <[email protected]>
Signed-off-by: Clarence Ng <[email protected]>
test passes with this PR: https://buildkite.com/ray-project/release-tests-pr/builds/27905#01863648-d64e-46d2-af29-cb3632b59e16 |
Let's merge! |
Personally don't prefer to have specialized config to nightly tests. Let's at least add this flag to the documentation and explain when it can be useful? |
|
@clarng @cadedaniel Let's do a 2.3 cherry pick PR for this? |
Signed-off-by: Clarence Ng <[email protected]> 3x nightly dask test is failing, due to enabling of group-by-owner oom killer policy This switches the test to use the previous policy Signed-off-by: Clarence Ng <[email protected]>
… (#32425) 3x nightly dask test is failing, due to enabling of group-by-owner oom killer policy This switches the test to use the previous policy Signed-off-by: Clarence Ng <[email protected]>
…project#32361) Signed-off-by: Clarence Ng <[email protected]> 3x nightly dask test is failing, due to enabling of group-by-owner oom killer policy This switches the test to use the previous policy Signed-off-by: Edward Oakes <[email protected]>
Signed-off-by: Clarence Ng [email protected]
Why are these changes needed?
3x nightly dask test is failing, due to enabling of group-by-owner oom killer policy
This switches the test to use the previous policy
Related issue number
#32195
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.