bazelbuild / bazelbuild/bazel

--watchfs should track output files, too

Open
#5,270 3 comments 2 reactions 0 assignees View on GitHub
help wanted not stale P3 team-Performance type: feature request
Dominant language
Java
Stars
25.8k
Forks
4.6k
Avg merge
2d 20h
Merged PRs (30d)
72

Description

`--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.

Contributor guide

Open the contributing guide

Research direction

Start by tracing how --watchfs avoids stating input files before a build, then compare that flow with the cached action-state validation that states known output files. Done means --watchfs also watches output files so those pre-execution output-file stats are no longer needed.

Written by the indexing model from the issue text.

Assessment

Domain
build-system
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.