зеркало из https://github.com/mozilla/gecko-dev.git
d42db71402
It can be a frustrating experience to push something to e.g. try, get build errors, fix them, and realize on a subsequent push that there were other build errors, but since the build failed as soon as it reached the first error, the logs didn't show them. While stopping at the first error locally is more helpful locally (although it still stop immediately and errors are often buried in the logs), it is actually desirable to avoid stopping on automation. Differential Revision: https://phabricator.services.mozilla.com/D154327 |
||
|---|---|---|
| .. | ||
| devtools/migrate-l10n | ||
| docs | ||
| gdbpp/gdbpp | ||
| l10n | ||
| lldbutils | ||
| mach | ||
| mozboot | ||
| mozbuild | ||
| mozlint | ||
| mozperftest | ||
| mozrelease | ||
| mozterm | ||
| mozversioncontrol | ||
| sites | ||
| 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