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
Running bazel query will invalidate the external repositories of bazel build and vice versa.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Run bazel build in a project with external repos.
Run bazel query, all repos will be fetched again. They will come from local cache but this still take a few seconds.
Run bazel build, again all repos will be invalidated and fetched.
What operating system are you running Bazel on?
Ubuntu 16.04
What's the output of bazel info release?
2.2.0 and all later version.
Any other information, logs, or outputs that you want to share?
Tracked this down to a3a2215. The newly added "STARLARK_SEMANTICS" in marker data is likely the cause. In bazel build, STARLARK_SEMANTICS is set while in bazel query it is empty so the market data is different.
The text was updated successfully, but these errors were encountered:
Description of the problem / feature request:
Running
bazel query
will invalidate the external repositories ofbazel build
and vice versa.Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
bazel build
in a project with external repos.bazel query
, all repos will be fetched again. They will come from local cache but this still take a few seconds.bazel build
, again all repos will be invalidated and fetched.What operating system are you running Bazel on?
Ubuntu 16.04
What's the output of
bazel info release
?2.2.0 and all later version.
Any other information, logs, or outputs that you want to share?
Tracked this down to a3a2215. The newly added "STARLARK_SEMANTICS" in marker data is likely the cause. In
bazel build
, STARLARK_SEMANTICS is set while inbazel query
it is empty so the market data is different.The text was updated successfully, but these errors were encountered: