Closed Bug 1441161 Opened 7 years ago Closed 7 years ago

Intermittent netwerk/test/unit/test_bug1355539_http1.js | check_response_id - [check_response_id : 98] "102" == 101

Categories

(Core :: Networking, defect, P3)

Product:
Core
Component:
Networking
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Assigned: mayhemer)

Details

(Keywords: intermittent-failure, Whiteboard: [necko-triaged])

Filed by: archaeopteryx [at] coole-files.de https://treeherder.mozilla.org/logviewer.html#?job_id=164314631&repo=try https://queue.taskcluster.net/v1/task/YgfuDELgT8SoRfi7pWVgTQ/runs/0/artifacts/public/logs/live_backing.log 12:30:52 INFO - TEST-START | netwerk/test/unit/test_bug1355539_http1.js 12:30:52 WARNING - TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_bug1355539_http1.js | xpcshell return code: 0 12:30:52 INFO - TEST-INFO took 188ms 12:30:52 INFO - >>>>>>> 12:30:52 INFO - (xpcshell/head.js) | test MAIN run_test pending (1) 12:30:52 INFO - (xpcshell/head.js) | test pending (2) 12:30:52 INFO - (xpcshell/head.js) | test pending (3) 12:30:52 INFO - (xpcshell/head.js) | test pending (4) 12:30:52 INFO - (xpcshell/head.js) | test pending (5) 12:30:52 INFO - (xpcshell/head.js) | test pending (6) 12:30:52 INFO - (xpcshell/head.js) | test pending (7) 12:30:52 INFO - (xpcshell/head.js) | test MAIN run_test finished (7) 12:30:52 INFO - running event loop 12:30:52 INFO - (xpcshell/head.js) | test pending (7) 12:30:52 INFO - (xpcshell/head.js) | test pending (8) 12:30:52 INFO - (xpcshell/head.js) | test pending (9) 12:30:52 INFO - (xpcshell/head.js) | test pending (10) 12:30:52 INFO - (xpcshell/head.js) | test pending (11) 12:30:52 INFO - (xpcshell/head.js) | test pending (12) 12:30:52 INFO - (xpcshell/head.js) | test finished (12) 12:30:52 INFO - (xpcshell/head.js) | test finished (11) 12:30:52 INFO - (xpcshell/head.js) | test finished (10) 12:30:52 INFO - (xpcshell/head.js) | test finished (9) 12:30:52 INFO - (xpcshell/head.js) | test finished (8) 12:30:52 INFO - (xpcshell/head.js) | test finished (7) 12:30:52 WARNING - TEST-UNEXPECTED-FAIL | netwerk/test/unit/test_bug1355539_http1.js | check_response_id - [check_response_id : 98] "102" == 101 12:30:52 INFO - Z:/task_1519647026/build/tests/xpcshell/tests/netwerk/test/unit/test_bug1355539_http1.js:check_response_id:98 12:30:52 INFO - Z:/task_1519647026/build/tests/xpcshell/tests/netwerk/test/unit/test_bug1355539_http1.js:setup_http_server/<:154 12:30:52 INFO - resource://testing-common/httpd.js:handleResponse:2379 12:30:52 INFO - resource://testing-common/httpd.js:process:1230 12:30:52 INFO - resource://testing-common/httpd.js:_handleResponse:1684 12:30:52 INFO - resource://testing-common/httpd.js:_processBody:1532 12:30:52 INFO - resource://testing-common/httpd.js:onInputStreamReady:1400 12:30:52 INFO - Z:\task_1519647026\build\tests\xpcshell\head.js:_do_main:221 12:30:52 INFO - Z:\task_1519647026\build\tests\xpcshell\head.js:_execute_test:533 12:30:52 INFO - -e:null:1 12:30:52 INFO - exiting test
This looks suspiciously similar to bug 1425512 (only the numbers differ). I wonder if the fix there didn't actually fix it 100% of the time? Any ideas, Honza (since you reviewed that bug)?
Flags: needinfo?(honzab.moz)
Priority: P5 → P3
Whiteboard: [necko-triaged]
I think the test is overly complicated and still a bit wrong. We should ensure there is always only one free connection to send a request from 'transactionQueue' out at the time. the test is finishing all dummy responses one by one (process a dummy response on the server -> onstop on the client -> process next dummy on the server -> etc), but this doesn't prevent a local connection racing of testing requests going out. This means a rewrite, I have some ideas how, but I really want to wait on how high is the rate of this intermittent first to prioritize.
Assignee: nobody → honzab.moz
Flags: needinfo?(honzab.moz)
https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.