[Data] Fail map_batches benchmark on worker OOM#63474
Merged
Merged
Conversation
Signed-off-by: Balaji Veeramani <bveeramani@berkeley.edu>
Contributor
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
TruongQuangPhat
pushed a commit
to cyhapun/ray-fix-issue
that referenced
this pull request
May 27, 2026
## Description The map_batches release benchmark had `RAYTEST_FAIL_ON_WORKER_OOM=0`. After we landed some changes to minimize memory bloat like ray-project#62302, the test no longer OOMs, so I'm re-enabling the flag. ## Related issues None Signed-off-by: Balaji Veeramani <bveeramani@berkeley.edu> Signed-off-by: phattruong <23120318@student.hcmus.edu.vn>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
The map_batches release benchmark had
RAYTEST_FAIL_ON_WORKER_OOM=0. After we landed some changes to minimize memory bloat like #62302, the test no longer OOMs, so I'm re-enabling the flag.Related issues
None