bazelbuild/bazel

--watchfs should track output files, too

Open

#5,270 opened on May 25, 2018

View on GitHub
 (3 comments) (2 reactions) (0 assignees)Java (4,465 forks)batch import
P3help wantednot staleteam-Performancetype: feature request

Repository metrics

Stars
 (25,384 stars)
PR merge metrics
 (Avg merge 22d 20h) (77 merged PRs in 30d)

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

Research direction
Study Bazel's watchfs implementation and the action cache invalidation mechanism. Focus on how output files are stated and propose a way to watch them instead.
Tech stack
java
Domain
build systembackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaBazel
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30