Changes to backend input files result in config.status during the build

NEW
Unassigned

Status

()

Core
Build Config
P1
normal
4 years ago
2 years ago

People

(Reporter: gps, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
I'm not sure when this regressed, but currently if a backend input file (e.g. a moz.build file) changes during a build, config.status will be executed during the build.

This is bad because it means the build config could diverge during a build and because checking whether the backend is up to date is resource intensive and slows down builds.
(Reporter)

Updated

4 years ago
Duplicate of this bug: 957955
You need to log in before you can comment on or make changes to this bug.