Description of the bug:
The screenshot below demonstrates inconsistent formatting:
Build progress bar "5,234 / 10,498" uses human readable formatting: comma before 3 digits.
"Analyzing: 1031 targets ..." uses simplified formatting: no separator before the groups of 3 digits.
Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Run any build with a large number of targets.
Which operating system are you running Bazel on?
Linux
What is the output of bazel info release?
release 8.6.0
If bazel info release returns development version or (@non-git), tell us how you built Bazel.
N/A
What's the output of git remote get-url origin; git rev-parse HEAD ?
N/A
If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
No response
Have you found anything relevant by searching the web?
No
Any other information, logs, or outputs that you want to share?
No response
Description of the bug:
The screenshot below demonstrates inconsistent formatting:
Build progress bar "5,234 / 10,498" uses human readable formatting: comma before 3 digits.
"Analyzing: 1031 targets ..." uses simplified formatting: no separator before the groups of 3 digits.
Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Run any build with a large number of targets.
Which operating system are you running Bazel on?
Linux
What is the output of
bazel info release?release 8.6.0
If
bazel info releasereturnsdevelopment versionor(@non-git), tell us how you built Bazel.N/A
What's the output of
git remote get-url origin; git rev-parse HEAD?N/A
If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
No response
Have you found anything relevant by searching the web?
No
Any other information, logs, or outputs that you want to share?
No response