Open
Bug 1028399
Opened 10 years ago
Updated 2 years ago
JS Debugger crashes under mochitests
Categories
(Testing :: Mochitest, defect)
Testing
Mochitest
Tracking
(Not tracked)
NEW
People
(Reporter: mt, Unassigned)
References
Details
Bug 995417 causes gecko to crash if it tries to connect to an external host while running mochitests. This is good, but the remote JS debugger still attempts to contact the update servers, triggering the crash.
This eventually crashes:
./mach mochitest-plain --jsdebugger foo
Comment 1•10 years ago
|
||
PSA: Use mach mochitest instead of mochitest-plain (it knows what the test flavors are)
Reporter | ||
Comment 2•10 years ago
|
||
(In reply to Gregory Szorc [:gps] from comment #1)
> PSA: Use mach mochitest instead of mochitest-plain (it knows what the test
> flavors are)
That doesn't work for me, is it that new?
Reporter | ||
Comment 3•10 years ago
|
||
More information:
243 INFO FATAL ERROR: Non-local network connections are disabled and a connection attempt to aus4.mozilla.org (63.245.217.219) was made.
about:config shows the following entries containing 'aus4':
app.update.certs.1.commonName;aus4.mozilla.org
app.update.certs.2.commonName;aus4.mozilla.org
app.update.url;https://aus4.mozilla.org/update/3/%PRODUCT%/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
media.gmp-manager.certs.1.commonName;aus4.mozilla.org
media.gmp-manager.certs.2.commonName;aus4.mozilla.org
media.gmp-manager.url;https://aus4.mozilla.org/update/3/GMP/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
Reporter | ||
Comment 4•10 years ago
|
||
106 INFO FATAL ERROR: Non-local network connections are disabled and a connection attempt to tiles.up.mozillalabs.com (2406:da00:ff00::4b65:a18f) was made.
Every. Single. Time.
Reporter | ||
Updated•10 years ago
|
Comment 5•10 years ago
|
||
Sounds like the jsdebugger isn't using prefs_general.js correctly (which have the appropriate prefs already stubbed out). That sounds like a better fix than anything related to bug 1049688.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•