mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-11-25 05:41:12 +00:00
f78ff6326c
The --no-sync flag turns off the SQLite synchronous pragma, so we don't force the disk to sync on every 'mach build'. Since mach always touches a few files (eg: warnings.json, .purgecaches, etc), there is always a minor amount of updates to the database, and syncing them every time just forces an unnecessary delay. The --debug-logging flag saves logs under .tup/log to show what files changes or were deleted, as well as the corresponding build DAG. This can be helpful when trying to investigate why something was rebuilt. MozReview-Commit-ID: L0m7IsYlFUI --HG-- extra : rebase_source : 0a26bf49778dfa13644f200be3e7061491b135c0 |
||
---|---|---|
.. | ||
devtools/migrate-l10n | ||
docs | ||
l10n/fluent_migrations | ||
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