Skip to content
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

query and build invalidate each other's external repositories #11895

Closed
manshengyang opened this issue Aug 5, 2020 · 2 comments
Closed

query and build invalidate each other's external repositories #11895

manshengyang opened this issue Aug 5, 2020 · 2 comments

Comments

@manshengyang
Copy link
Contributor

Description of the problem / feature request:

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.

  1. Run bazel build in a project with external repos.
  2. Run bazel query, all repos will be fetched again. They will come from local cache but this still take a few seconds.
  3. 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.

@benjaminp
Copy link
Collaborator

Yep, see #10961.

@jin
Copy link
Member

jin commented Aug 6, 2020

Thanks @benjaminp, closing as dupe of #10961.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants