You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found at the end of a build for a somewhat large project, that all compiling and linking tasks were complete, but bear still had a citnames process burning a full single core worth of CPU for 8 to 10 minutes before the build finally completed.
To Reproduce
Probably a little difficult since I can't give you access to the source.
Expected behavior
This process takes so long, without any feedback that users will think the build is permanently stuck. They may not be able to identify that bear is causing this.
This is likely similar to #486 (they didn't wait long enough?)
I understand that this may be normal and due to the amount of processing that needs to occur, it may be adequate to print some progress feedback and ETA.
Environment:
OS name: Debian bullseye
OS version: 11
OS architecture: arm64 cross compiler in an x86_64 environment
Bear version: 3.0.8
Bear install method: package
Additional context
timo 2651108 0.0 0.0 6580 4192 ? S 14:41 0:00 \_ bear --append --output clientarm64.mak.compile_commands.json -- make -f clientarm64.mak -j12 all-targets
timo 2947683 99.2 0.9 326492 315636 ? R 15:05 7:35 \_ /usr/bin/citnames --input clientarm64.mak.compile_commands.sqlite3 --output clientarm64.mak.compile_commands.json --run-checks --append
The text was updated successfully, but these errors were encountered:
Describe the bug
I found at the end of a build for a somewhat large project, that all compiling and linking tasks were complete, but
bear
still had acitnames
process burning a full single core worth of CPU for 8 to 10 minutes before the build finally completed.To Reproduce
Probably a little difficult since I can't give you access to the source.
Expected behavior
This process takes so long, without any feedback that users will think the build is permanently stuck. They may not be able to identify that bear is causing this.
This is likely similar to #486 (they didn't wait long enough?)
I understand that this may be normal and due to the amount of processing that needs to occur, it may be adequate to print some progress feedback and ETA.
Environment:
Additional context
The text was updated successfully, but these errors were encountered: