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

buildbox-casd and buildbox-fuse mismatch when having both wheel and system installed versions #1970

Open
abderrahim opened this issue Nov 20, 2024 · 1 comment

Comments

@abderrahim
Copy link
Contributor

When having buildbox installed in the PATH and in the wheel, buildstream mismatches them. IIRC, it will use the buildbox-casd from the PATH and buildbox-fuse from the wheel.

If the two versions are incompatible, this can result in a buildstream crash with the error:

    grpc._channel._MultiThreadedRendezvous: <_MultiThreadedRendezvous of RPC that terminated with:
        status = StatusCode.INTERNAL
        details = "std::runtime_error exception thrown at [buildboxcasd_fusestager.cpp:144], errMsg = "The FUSE stager child process unexpectedly died with exit code 1""
        debug_error_string = "UNKNOWN:Error received from peer  {created_time:"2024-11-20T09:16:31.255363002+00:00", grpc_status:13, grpc_message:"std::runtime_error exception thrown at [buildboxcasd_fusestager.cpp:144], errMsg = \"The FUSE stager child process unexpectedly died with exit code 1\""}"
@nanonyme
Copy link
Contributor

nanonyme commented Dec 11, 2024

Might be I created a regression trying to make BuildStream prefer buildbox from PATH. Or did I never manage to land the change that would prefer PATH always.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants