Closed SunJun8 closed 2 years ago
Thanks for the report @SunJun8 .
Is there any chance that you can use the latest version of this tool? Maybe compile it against a recent version of gRPC?
The are too many open file descriptor, which is a result of a gRPC bug (search their github issues, I think it's still open). As a workaround, you can increase the number of open file descriptors. (See limit
command.)
I'm closing this ticket, because I can't do much about this problem in this project. (Other than not using gRPC, but that's a long term plan.)
Thanks for the report @SunJun8 .
Is there any chance that you can use the latest version of this tool? Maybe compile it against a recent version of gRPC?
The are too many open file descriptor, which is a result of a gRPC bug (search their github issues, I think it's still open). As a workaround, you can increase the number of open file descriptors. (See
limit
command.)I'm closing this ticket, because I can't do much about this problem in this project. (Other than not using gRPC, but that's a long term plan.)
Thanks Reply
I just want to know whether bear can directly circumvent this problem, rather than modify fd limit, but this is indeed the most direct way to solve the problem
Reducing the parallelism of your build can mitigate the problem too.
Reducing the parallelism of your build can mitigate the problem too.
Yes, but this is a waste of my precious cpu core
Describe the bug I use 16-core cpu to compile the code in wsl2 and it appears:
To Reproduce using CPU with 16 cores or more to compile code
Expected behavior same as above
Environment:
Additional context
bear -- make CPU_ID=M1 CONFIG_LINK_RAM=1 CONFIG_LINK_ROM=0 -j