зеркало из https://github.com/mozilla/gecko-dev.git
8e4cf752da
AFAIK, while mochitests have resource-usage.json data with the same format as build_resources.json, there isn't much of anything to display that data in a human-friendly manner. As a helper of sort for all the tasks that already expose their json data without a nice way to display it, allow the build resources usage report UI that `mach resource-usage` displays (or build_resources.html on build tasks on treeherder), to load arbitrary json files if their url is dropped on the page (from e.g. drag-and-dropping the link to the file from treeherder). Differential Revision: https://phabricator.services.mozilla.com/D109030 |
||
|---|---|---|
| .. | ||
| 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