bazel aquery returns same ActionKey even when file contents have changed #11718
Labels
P2
We'll consider working on this in future. (Assignee optional)
team-Documentation
Documentation improvements that cannot be directly linked to other team labels
team-Performance
Issues for Performance teams
type: bug
type: documentation (cleanup)
Description of the problem / feature request:
When running
bazel aquery
for a target, the actions that take source files as inputs show anActionKey
that does not change even when the contents of one or more input source files has changed. I would expect theActionKey
to be a different hash when the contents have changed.This seems to me like either user error on my part, or a bug with
aquery
, because I have not seen this result in a stale build where changes don't get picked up.Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
I have a minimal repro project here:
action_key_repro.zip
Running
bazel aquery 'deps(//:foo)' --nohost_deps --notool_deps --noimplicit_deps
gives me the output with the following for the "Compiling lib/print.cpp" action:If I then modify
lib/print.cpp
by changing the "hello world" string to something else and save it, re-runningbazel aquery
as described above gives me the exact same output, with the sameActionKey
.What operating system are you running Bazel on?
macOS 10.15.5
What's the output of
bazel info release
?Have you found anything relevant by searching the web?
--check_up_to_date
option --bazel build --check_up_to_date //:foo
correctly reports that it is out of date after I changelib/print.cpp
, so this works as expected even when theActionKey
doesn't changebazel build
orbazel shutdown
prior to re-checking the output ofbazel aquery
does not helpAny other information, logs, or outputs that you want to share?
Minimal repro project: action_key_repro.zip
The text was updated successfully, but these errors were encountered: