mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-28 04:35:33 +00:00
e01aaa0155
The TestManifestBackend always has a dependency on config.status, even if configure hasn't been run yet. If configure is run later, this is intended to cause the TestManifestBackend to be regenerated so that it can use the configured values instead of a potentially incomplete setup. Mozbuild's backend_out_of_date() logic treats a missing file as always being out of date, which means if configure hasn't run, the TestManifestBackend will always be regenerated. Instead we can create a stub config.status file that will fix the out-of-date check, and can be treated as a BuildEnvironmentNotFoundException as if the file didn't exist at all. Differential Revision: https://phabricator.services.mozilla.com/D27195 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| devtools/migrate-l10n | ||
| docs | ||
| l10n | ||
| mach | ||
| mozboot | ||
| mozbuild | ||
| mozlint | ||
| mozrelease | ||
| mozterm | ||
| mozversioncontrol | ||
| safety | ||
| mach_commands.py | ||
| moz.build | ||
| README | ||
This directory contains common Python code. The basic rule is that if Python code is cross-module (that's "module" in the Mozilla meaning - as in "module ownership") and is MPL-compatible, it should go here. What should not go here: * Vendored python modules (use third_party/python instead) * Python that is not MPL-compatible (see other-licenses/) * Python that has good reason to remain close to its "owning" (Mozilla) module (e.g. it is only being consumed from there). Historical information can be found at https://bugzilla.mozilla.org/show_bug.cgi?id=775243 https://bugzilla.mozilla.org/show_bug.cgi?id=1346025