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

--watchfs should track output files, too #5270

Open
benjaminp opened this issue May 25, 2018 · 3 comments
Open

--watchfs should track output files, too #5270

benjaminp opened this issue May 25, 2018 · 3 comments
Labels
help wanted Someone outside the Bazel team could own this not stale Issues or PRs that are inactive but not considered stale P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Performance Issues for Performance teams type: feature request

Comments

@benjaminp
Copy link
Collaborator

benjaminp commented May 25, 2018

--watchfs avoids stating input files in the package path before every build. However, Bazel still checks the validity of cached action state by stating all the action output files it knows about. It would be nice if --watchfs could watch output files and obviate stating all of them before execution starts.

@ulfjack
Copy link
Contributor

ulfjack commented Jun 4, 2018

The --watchfs infrastructure needs to be rewritten and made more generic, and yes, it should absolutely support output tree tracking as well. It's been on my todo list for a long time. :-/

@ulfjack ulfjack removed their assignment Nov 20, 2018
@ulfjack
Copy link
Contributor

ulfjack commented Nov 20, 2018

I'm afraid I won't be able to work on this.

@meisterT meisterT added P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Performance Issues for Performance teams and removed category: performance labels Nov 29, 2018
@meisterT meisterT added the help wanted Someone outside the Bazel team could own this label May 11, 2020
@github-actions
Copy link

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 2.5 years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

@github-actions github-actions bot added the stale Issues or PRs that are stale (no activity for 30 days) label Mar 16, 2023
@fmeum fmeum added not stale Issues or PRs that are inactive but not considered stale and removed stale Issues or PRs that are stale (no activity for 30 days) labels Mar 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Someone outside the Bazel team could own this not stale Issues or PRs that are inactive but not considered stale P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Performance Issues for Performance teams type: feature request
Projects
None yet
Development

No branches or pull requests

5 participants