Open Bug 1104005 Opened 8 years ago Updated 5 years ago
Can't run "./mach test browser/devtools/webconsole/test/browser
_webconsole _block _mixedcontent _securityerrors .js" because of python issues in mach _commands .py
$ ./mach test browser/devtools/webconsole/test/browser_webconsole_block_mixedcontent_securityerrors.js From _tests: Kept 33899 existing; Added/updated 3; Removed 0 files and 0 directories. TEST-INFO | checking window state Browser Chrome Test Summary Passed: 0 Failed: 0 Todo: 0 *** End BrowserChrome Test Results *** Error running mach: ['test', 'browser/devtools/webconsole/test/browser_webconsole_block_mixedcontent_securityerrors.js'] The error occurred in code that was called by the mach command. This is either a bug in the called code itself or in the way that mach is calling it. You should consider filing a bug for this issue. If filing a bug, please include the full output of mach, including this error message. The details of the failure are as follows: UnboundLocalError: local variable 'result' referenced before assignment File "e:\dev\fx-team\testing/mach_commands.py", line 239, in test test_objects=tests, **m['kwargs']) File "e:\dev\fx-team\python/mach\mach\registrar.py", line 62, in dispatch return fn(**args) or 0 File "e:\dev\fx-team\testing/mochitest/mach_commands.py", line 765, in run_mochitest_general **kwargs) File "e:\dev\fx-team\testing/mochitest/mach_commands.py", line 390, in run_desktop_test result = runner.runTests(options) File "e:\dev\builds\opt-i686-pc-mingw32\_tests\testing\mochitest\runtests.py", line 1764, in runTests return result -------------------------------------- AFAICT from the manifest and my directory's state, the test exists and should be runnable on this platform. This is on Windows 8.1, with 3 patches applied on top of 216800:da918fa50e5f on fx-team. Python 2.7.5 (default, May 15 2013, 22:43:36) [MSC v.1500 32 bit (Intel)] on win32
The test runs normally if I substitute "mochitest-devtools" for "test".
Component: mach → Mochitest
Product: Core → Testing
You need to log in before you can comment on or make changes to this bug.