Jeremiah Rodriguez

I hit the same issue after an Arch Linux update. You need to increase the kernel file limits before opening. Before: ``` # Current open file limit is 1024 [jeremiah@jeremiah...

The number of inodes on /dev/shm is 95M. Before removing the sandbox directory, there were 1700 free (it's not 0 because Bazel cleans some up before I check the number.)...

It takes around 65 seconds to run out of inodes when the build is running. Once the build fails, if I just leave Bazel alone to clean up the sandbox...

> In general it seems off to me that we generate inodes based on jobs (typically CPU count) but don't scale cleanup based on CPUs. So the more powerful your...

> The reason you give sounds logical. A single deletion thread cannot keep up. > > Something else I was wondering, do you have `--reuse_sandbox_directories` enabled? That should in theory...

I tested a full rebuild of my project with Bazel 7.1.0 RC1. The result is that the build is actually able to complete now without specifying ```--experimental_sandbox_async_tree_delete_idle_threads=0```. The inode usage...

I ran a few full rebuilds of my project: * Bazel 7.0.2 + ```--experimental_sandbox_async_tree_delete_idle_threads=0``` * Completes in 2254 seconds * Output of your command: 20925239343 * Bazel 7.1.0rc1 + ```--experimental_sandbox_async_tree_delete_idle_threads=0```...