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.

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

[Bug] build ray project on arch64 #19865

Closed
2 tasks done
hecheng64 opened this issue Oct 29, 2021 · 3 comments
Closed
2 tasks done

[Bug] build ray project on arch64 #19865

hecheng64 opened this issue Oct 29, 2021 · 3 comments
Labels
bug Something that is supposed to be working; but isn't stale The issue is stale. It will be closed within 7 days unless there are further conversation triage Needs triage (eg: priority, bug/not-bug, and owning component)

Comments

@hecheng64
Copy link

Search before asking

  • I searched the issues and found no similar issues.

Ray Component

Others

What happened + What you expected to happen

I followed (https://docs.ray.io/en/master/development.html#building-ray-full ) the operation on arch64 centos8, but the following problems occurred:
INFO: Deleting stale sandbox base /root/.cache/bazel/_bazel_root/2342e7b33aca58abb45809f4e4067d31/sandbox
[25 / 1,878] 8 actions running
Compiling src/compiler/python_generator.cc [for host]; 51s processwrapper-sandbox
Compiling src/google/protobuf/util/message_differencer.cc [for host]; 51s processwrapper-sandbox
Compiling src/compiler/node_generator.cc [for host]; 37s processwrapper-sandbox
Compiling src/google/protobuf/compiler/cpp/cpp_helpers.cc [for host]; 29s processwrapper-sandbox
Compiling src/google/protobuf/compiler/cpp/cpp_message.cc [for host]; 28s processwrapper-sandbox
Compiling src/google/protobuf/compiler/cpp/cpp_padding_optimizer.cc [for host]; 10s processwrapper-sandbox
Compiling src/google/protobuf/compiler/cpp/cpp_primitive_field.cc [for host]; 5s processwrapper-sandbox
Compiling src/google/protobuf/compiler/cpp/cpp_service.cc [for host]; 3s processwrapper-sandbox

Server terminated abruptly (error code: 14, error message: 'Socket closed', log file: '/root/.cache/bazel/_bazel_root/2342e7b33aca58abb45809f4e4067d31/server/jvm.out')

Versions / Dependencies

ray: the lastest
python :3.7
os; centos8
arch:aarch64 or arm64

Reproduction script

(https://docs.ray.io/en/master/development.html#building-ray-full

Anything else

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!
@hecheng64 hecheng64 added bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component) labels Oct 29, 2021
@stale
Copy link

stale bot commented Feb 26, 2022

Hi, I'm a bot from the Ray team :)

To help human contributors to focus on more relevant issues, I will automatically add the stale label to issues that have had no activity for more than 4 months.

If there is no further activity in the 14 days, the issue will be closed!

  • If you'd like to keep the issue open, just leave any comment, and the stale label will be removed!
  • If you'd like to get more attention to the issue, please tag one of Ray's contributors.

You can always ask for help on our discussion forum or Ray's public slack channel.

@stale stale bot added the stale The issue is stale. It will be closed within 7 days unless there are further conversation label Feb 26, 2022
@stale
Copy link

stale bot commented Mar 15, 2022

Hi again! The issue will be closed because there has been no more activity in the 14 days since the last message.

Please feel free to reopen or open a new issue if you'd still like it to be addressed.

Again, you can always ask for help on our discussion forum or Ray's public slack channel.

Thanks again for opening the issue!

@stale stale bot closed this as completed Mar 15, 2022
@ddelange
Copy link
Contributor

duplicate of #12128

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that is supposed to be working; but isn't stale The issue is stale. It will be closed within 7 days unless there are further conversation triage Needs triage (eg: priority, bug/not-bug, and owning component)
Projects
None yet
Development

No branches or pull requests

2 participants