488611 - Determine why Windows is stupid and reenable test_start_stop.js there

Status: NEW

(Testing :: General, defect)

Description

[Jeff Walden [:Waldo]]

NEXT ERROR TEST-UNEXPECTED-FAIL | e:\builds\moz2_slave\mozilla-central-win32-unittest\build\objdir\_tests\xpcshell\test_necko\test\test_start_stop.js | test failed, see following log:
  >>>>>>>
  ### XPCOM_MEM_LEAK_LOG defined -- logging leaks to c:\docume~1\cltbld\locals~1\temp\runxpcshelltests_leaks.log
*** test pending
*** run_test
>>> listening on port 4444
*** test pending
>>> stopping listening on port 4444
*** test finished
*** running event loop
>>> shutting down server on port 4444
*** no open connections, notifying async from onStopListening
*** _notifyStopped async callback
*** test pending
*** run_test_2
*** test finished
>>> listening on port 4444
>>> listening on port 4444
*** exiting

Windows is allowing me to have two nsIServerSocket components initialized with the same port number and to call asyncListen on both of them without either call throwing an exception.  Don't know why this is, can't debug without testing on a Windows box, so disabled on Windows and will fix here...

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee is inactive on Bugzilla, so the assignee is being reset.