mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-16 14:55:47 +00:00
5c85018da7
In bug 1461714 we run node.py to generate main.js in the objdir, and use FINAL_TARGET_FILES to install it into dist. However, when both rules are run in parallel in the misc tier, the install target may pick up the main.js file from the srcdir via VPATH, so we end up with the wrong file in dist. This causes some mochitests to fail with "uncaught exception - SyntaxError: import declarations may only appear at top level of a module at @resource://devtools/client/debugger/new/src/main.js:7:undefined" The workaround here is to run these node.py invocations (which always write to node.stub) in the export tier, so that when the install target in misc is processed, the objdir version of the file is always present and takes precedence. A better fix would probably be to remove our reliance on VPATH, and just pass in the path to files in the srcdir when they are required. That could potentially be a major overhaul, however. MozReview-Commit-ID: JZ04C7zJPbX Differential Revision: https://phabricator.services.mozilla.com/D7770 --HG-- extra : moz-landing-system : lando |
||
---|---|---|
.. | ||
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