bazelbuild/bazel

Incremental build fails (missing dep declarations for std lib), requires expunge

Open

#11,200 opened on Apr 22, 2020

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Java (4,465 forks)batch import
P4help wantedteam-Documentationteam-Rules-CPPtype: documentation (cleanup)

Repository metrics

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

Description

With incremental builds, I see errors like

ERROR: /usr/local/google/home/gcmn/.cache/bazel/_bazel_gcmn/151032d5e60e04f24eb0914f43c91bbf/external/com_google_absl/absl/base/BUILD.bazel:145:1: undeclared inclusion(s) in rule '@com_google_absl//absl/base:malloc_internal':
this rule is missing dependency declarations for the following files included by 'external/com_google_absl/absl/base/internal/low_level_alloc.cc':
  '/usr/lib/clang/9.0.1/include/stddef.h'
  '/usr/lib/clang/9.0.1/include/stdint.h'
  '/usr/lib/clang/9.0.1/include/limits.h'
  '/usr/lib/clang/9.0.1/include/__stddef_max_align_t.h'
  '/usr/lib/clang/9.0.1/include/stdarg.h'

The specific starting point varies (not always absl), but it's always an include of some std header. Building with RBE worked, so I think it's something specific about the local state. bazel clean was insufficient to fix the issue, but bazel clean --expunge made it go away. Per the instructions at https://docs.bazel.build/versions/master/user-manual.html#the-clean-command, I'm filing a bug.

Please let me know what additional information I can provide, although I suspect some things may be lost now that I've run expunge.

Contributor guide

Research direction
Reproduce the issue by running an incremental build after a clean build with local execution. Inspect the missing header errors and trace why Bazel fails to include them in the dependency graph. Consider the role of action caching and header scanning.
Tech stack
java
Domain
build system
Issue type
Bug
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-3 hours
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
BazelGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40