-
Notifications
You must be signed in to change notification settings - Fork 101
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
Bazel test fails because of OSFamily
property not defined
#576
Comments
OSFamily
property not defined
Can you share the .json file you are using? |
Which JSON file you mean by?
|
I see... @aaronmondal , it looks like we missed some:
We need to add
|
Thanks, it works. 👍 |
5 tasks
Yeah we must have missed this in #512. Thanks @steed924! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I ran into this issue when I try to re-install this project on my Linux VPS - Ubuntu 22.0.4.
I installed Git, Rust, Docker, Cargo and Bazel on the pure VPS.
It successfully ran the nativelink server with
cargo run
command.But when I ran
bazel test
command it shows this error message and fails.`
It seems like because it couldn't get platform property of 'OSFamily' while implementing local remote execution feature and it has strict bazel build requirement.
I used to face error while I was running
bazel test
on my Windows machine also.Is it possible to set our local remote execution module not to affect the whole project's
bazel test
command?Or do we just need to refine our local remote execution module to match various OS family including Windows, MacOS and various machines including Cloud VPS?
Here is the screenshot of the error.
The text was updated successfully, but these errors were encountered: