-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Open
Labels
team-BazelGeneral Bazel product/strategy issuesGeneral Bazel product/strategy issuesteam-CoreSkyframe, bazel query, BEP, options parsing, bazelrcSkyframe, bazel query, BEP, options parsing, bazelrctype: buguntriaged
Description
Description of the bug:
On my repo, a build logged the following message:
INFO: Analyzed 5 targets (2781 packages loaded, 279953 targets and 384 aspects configured)
I was surprised by the 384 aspects until Fabian explained that it's not 384 different aspect implementations, but 384 targets touched by aspects.
How about the following rewording (or something similar) to make things clearer?
INFO: Analyzed 5 targets (2781 packages loaded, 280337 targets configured (384 by aspects))
Another (slightly longer) option would be
INFO: Analyzed 5 targets (2781 packages loaded, 279953 targets configured, 384 targets visited by aspects)
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.
No response
Which operating system are you running Bazel on?
No response
What is the output of bazel info release?
No response
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 HEAD ?
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 response
Any other information, logs, or outputs that you want to share?
cc @fmeum
Metadata
Metadata
Assignees
Labels
team-BazelGeneral Bazel product/strategy issuesGeneral Bazel product/strategy issuesteam-CoreSkyframe, bazel query, BEP, options parsing, bazelrcSkyframe, bazel query, BEP, options parsing, bazelrctype: buguntriaged