зеркало из https://github.com/mozilla/gecko-dev.git
1266f6cfb7
The `AUTOCLOBBER` mozconfig option is reliably causing builds to fail when a clobber is triggered. When we auto-clobber a build we do so after running `configure` but before running `make client.mk`. This means we destroy all the gathered information from the `configure` step in the objdir and then attempt to run `make` using the previously destroyed information. This commit moves the call to `_check_clobber` to an earlier stage in the build process, before `configure` is called, so any clobber that takes place will happen before setting up the objdir via `configure`. Since `_check_clobber` is only called once in the codebase, and both cases are now adding clobber metrics one after another, we remove the metrics gathering from `_check_clobber` and rely on callers to set metrics instead. Also clean up some nested `if` statements that can be flattened. Differential Revision: https://phabricator.services.mozilla.com/D100794 |
||
---|---|---|
.. | ||
devtools/migrate-l10n | ||
docs | ||
gdbpp/gdbpp | ||
l10n | ||
lldbutils | ||
mach | ||
mozboot | ||
mozbuild | ||
mozlint | ||
mozperftest | ||
mozrelease | ||
mozterm | ||
mozversioncontrol | ||
README | ||
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