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

I/O exception during sandboxed execution #17038

Open
liyuyun-lyy opened this issue Dec 16, 2022 · 2 comments
Open

I/O exception during sandboxed execution #17038

liyuyun-lyy opened this issue Dec 16, 2022 · 2 comments
Labels
more data needed P3 We're not considering working on this, but happy to review a PR. (No assignee) stale Issues or PRs that are stale (no activity for 30 days) team-Rules-CPP Issues for C++ rules

Comments

@liyuyun-lyy
Copy link

Description of the bug:

I'm using Bazel to build C++, with setting --sandbox_base=/mnt/ram/ and make directory /mnt/ram as ramfs. And I can get this I/O error sometimes, I still cannot find any routine to reproduce this bug, because the same source code may end with success or fail randomly. Is there any way to get more info about this error?
ioexception

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

No response

Which operating system are you running Bazel on?

linux

What is the output of bazel info release?

5.2.0

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse master; git rev-parse HEAD ?

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response

@sgowroji
Copy link
Member

Hello @liyuyun-lyy, Could you please share minimum steps required to reproduce the above issue!!

@buildbreaker2021 buildbreaker2021 added the P3 We're not considering working on this, but happy to review a PR. (No assignee) label Feb 10, 2023
Copy link

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 90 days unless any other activity occurs. If you think this issue is still relevant and should stay open, please post any comment here and the issue will no longer be marked as stale.

@github-actions github-actions bot added the stale Issues or PRs that are stale (no activity for 30 days) label Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
more data needed P3 We're not considering working on this, but happy to review a PR. (No assignee) stale Issues or PRs that are stale (no activity for 30 days) team-Rules-CPP Issues for C++ rules
Projects
None yet
Development

No branches or pull requests

3 participants