Closed Bug 804912 Opened 13 years ago Closed 12 years ago

Intermittent test_protocolproxyservice.js | test failed (with xpcshell return code: 0), | 127.0.0.1 != 127.0.0.1 - See following stack

Categories

(Core :: Networking, defect)

Product:
Core
Component:
Networking
Version:
17 Branch
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure)

https://tbpl.mozilla.org/php/getParsedLog.php?id=16389621&tree=Firefox Rev5 MacOSX Mountain Lion 10.8 mozilla-central debug test xpcshell on 2012-10-23 12:48:59 PDT for push a517f7ea5bef slave: talos-mtnlion-r5-038 TEST-UNEXPECTED-FAIL | /builds/slave/talos-slave/test/build/xpcshell/tests/netwerk/test/unit/test_protocolproxyservice.js | test failed (with xpcshell return code: 0), see following log: >>>>>>> ... TEST-PASS | /builds/slave/talos-slave/test/build/xpcshell/tests/netwerk/test/unit/test_protocolproxyservice.js | [myipaddress_callback : 597] 127.0.0.1 != null TEST-UNEXPECTED-FAIL | /builds/slave/talos-slave/test/build/xpcshell/tests/netwerk/test/unit/test_protocolproxyservice.js | 127.0.0.1 != 127.0.0.1 - See following stack: JS frame :: /builds/slave/talos-slave/test/build/xpcshell/head.js :: do_throw :: line 451 JS frame :: /builds/slave/talos-slave/test/build/xpcshell/head.js :: _do_check_neq :: line 507 JS frame :: /builds/slave/talos-slave/test/build/xpcshell/head.js :: do_check_neq :: line 528 JS frame :: /builds/slave/talos-slave/test/build/xpcshell/tests/netwerk/test/unit/test_protocolproxyservice.js :: myipaddress_callback :: line 598 JS frame :: /builds/slave/talos-slave/test/build/xpcshell/tests/netwerk/test/unit/test_protocolproxyservice.js :: <TOP_LEVEL> :: line 152 native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0 TEST-INFO | (xpcshell/head.js) | exiting test
Whiteboard: [orange]
Be interesting to see a graph of instances of this versus bustage in DNS in the build network.
BTW: This test failure occurs on like every test run on the SeaMonkey Mac OS X 10.6 test box (just in case someone wants to work on this/check something). Maybe it's another problem though as it's not intermittent, but looks like a permanent failure.
Actually it looks like this test failure depends quite a bit on what machine (and network connection) it is running on.
Closing inactive keywords:intermittent-failure bugs where the TBPLbot has previously commented and the test isn't marked as disabled; filter on orange-cleanup-201401.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.