-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building a target with a Bazel aspect overwrites the Target command line printout #10530
Comments
I am experiencing this too, using an internal type checking aspect similar to this mypy one.
Which makes it very difficult to know what outputs different rules create when I am uncertain how the rules work. I am also glad there seems to be a recent PR for #8739, because the suggestion to just look at I recognize that this is marked P3 and unlikely to get picked up, does the Bazel team have an idea of an acceptable way this could be implemented? I'd be open to submitting a PR. Looking at the code it seems to do
Would it be acceptable to add an or-condition to the first arm? Like
|
This should work around bazelbuild/bazel#10530.
This should work around bazelbuild/bazel#10530.
Description of the problem / feature request:
Building a target with a Bazel aspect overwrites the Target command line
printout. The Target printout previously contained information such as the
path to the generated build artifact.
For example:
Has a different command line output then
The path to the aspect build artifact is printed, but the original build artifact path is lost.
I believe this issue is related to this [logic](https://source.bazel.build/bazel/+/master:src/main/java/com/google/devtools/build/lib/buildtool/BuildResultPrinter.java;bpv=;l=81 l) in Bazel.
Feature requests: what underlying problem are you trying to solve with this feature?
Building a Bazel target with an aspect should preserve the build target output message.
What operating system are you running Bazel on?
darwin18.0
What's the output of
bazel info release
?release 1.1.0
Have you found anything relevant by searching the web?
I haven't found a relevant discussion online as of yet.
I believe this issue is related to this [logic](https://source.bazel.build/bazel/+/master:src/main/java/com/google/devtools/build/lib/buildtool/BuildResultPrinter.java;bpv=;l=81 l) in Bazel.
The text was updated successfully, but these errors were encountered: