Skip to content

[core] Ray build failure due to noop refactoring #52399

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
Open
dentiny opened this issue Apr 17, 2025 · 0 comments · May be fixed by #52400
Open

[core] Ray build failure due to noop refactoring #52399

dentiny opened this issue Apr 17, 2025 · 0 comments · May be fixed by #52400
Labels
community-backlog core Issues that should be addressed in Ray Core enhancement Request for new feature and/or capability

Comments

@dentiny
Copy link
Contributor

dentiny commented Apr 17, 2025

Description

PR #52250 is working on splitting large bazel targets into smaller ones to accelerate compilation speed and cache hit rate.

But CI keeps failing due to OOM:

[2025-04-17T05:33:59Z] Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
[2025-04-17T05:33:59Z] gcc: fatal error: Killed signal terminated program cc1plus

Link: https://buildkite.com/ray-project/premerge/builds/38454

Use case

No response
@dentiny dentiny added core Issues that should be addressed in Ray Core enhancement Request for new feature and/or capability triage Needs triage (eg: priority, bug/not-bug, and owning component) labels Apr 17, 2025
@dentiny dentiny linked a pull request Apr 17, 2025 that will close this issue
Open
@edoakes edoakes removed the triage Needs triage (eg: priority, bug/not-bug, and owning component) label Apr 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
community-backlog core Issues that should be addressed in Ray Core enhancement Request for new feature and/or capability
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use large instance for OOM test dentiny/ray
3 participants
@edoakes @dentiny @hainesmichaelc