fishrockz commented on issue #1885: URL: https://github.com/apache/buildstream/issues/1885#issuecomment-1854789837
This is really interesting. Thanks for the report! TLDR; AFAICT this is a bug in [buildbox-fuse](https://gitlab.com/BuildGrid/buildbox/buildbox-fuse) or [buildbox-casd](https://gitlab.com/BuildGrid/buildbox/buildbox-casd) @juergbi do you know which needs the issue raised? Long story: A tiny nit is that bst does not use a container as such, its using buildbox and boublewrap, but its not far off a container lol Another note is that buildbox records the build into the cache which uses the google REAPI formate only store the execution bit. [FileNode](https://girderstream.gitlab.io/girderstream/doc/girderstream/build_api/bazel/remote/execution/v2/struct.FileNode.html) So just fixing the crash will not allow for your use case.. You may note that the cache can store more info in the optional [NodeProperties](https://girderstream.gitlab.io/girderstream/doc/girderstream/build_api/bazel/remote/execution/v2/struct.NodeProperties.html) @juergbi explained to me that this optional data will be correctly staged but that buildbox does not record this optional info. I would like to add this extra info also, i have had a look at buildbox recently but i have not made much progress. related issues include https://github.com/apache/buildstream/issues/1790 https://github.com/apache/buildstream/issues/1792 https://github.com/apache/buildstream/issues/1413 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
