Closed Bug 1525468 Opened 5 years ago Closed 5 years ago

windows/aarch64 - web-platform-test | bad HTTP request errors

Categories

(Testing :: web-platform-tests, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: egao, Unassigned)

References

Details

Treeherder: https://treeherder.mozilla.org/#/jobs?repo=try&revision=7f2edbc029097dc7ca3c14f2ae488e4d7275d147

Taskcluster: https://tools.taskcluster.net/groups/efMBjsn0Q66A2tvOdHEHDw

Following entries in the log were seen for win10/aarch64 run of the WPT. They do not appear to have been reported previously.

22:18:46 CRITICAL - Test harness output was not a valid structured log message: 
22:18:46 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] code 400, message Bad request version ('\xbf?*R\x88\x00$\x13\x01\x13\x03\x13\x02\xc0+\xc0/\xcc\xa9\xcc\xa8\xc0,\xc00\xc0')
22:18:46 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] "ŭ_qzezE.{@(6 DPfEgڈaP+
22:18:46 CRITICAL - ?*R$+/̨̩,0" 400 -
22:18:46 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] code 400, message Bad HTTP/0.9 request type ('\x16\x03\x01\x02\x00\x01\x00\x01\xfc\x03\x03\xbe\xaf/\xf2\xf5\xb2\xbe\xcf\xe68D\x17\xc5\xd6;U\xdd\xeb\x1f\xff\xea%\x04oj[}\xe6\x04\xd7h+')
22:18:46 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] "/8D;U%oj[}h+ ݏM
22:18:46 CRITICAL - :~Z0k(jPT+$+/̨̩,0" 400 -
22:18:46 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] code 400, message Bad request version ('\xc8<c\xec\xfd\x8d\x14{-\x1bp^\xfe\xe3\xcf\xbc\xc5\xb0FD\x8e\x0eS\xe9\x1e\x9a\xb6)\xcc\xfb&\x08\x00$\x13\x01\x13\x03\x13\x02\xc0+\xc0/\xcc\xa9\xcc\xa8\xc0,\xc00\xc0')
22:18:46 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] "nt'gU	JE5|
22:18:46 CRITICAL - s/+ <c{-p^ϼŰFDS
22:18:46 CRITICAL - )&$+/̨̩,0" 400 -
22:18:47 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] code 400, message Bad request version ('\xfeK\xa2\xeeI\x00$\x13\x01\x13\x03\x13\x02\xc0+\xc0/\xcc\xa9\xcc\xa8\xc0,\xc00\xc0')
22:18:47 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] "xyҊ?%ׇS?
22:18:47 CRITICAL - (9Ċ/BMWL[ I¢t=byt$r<u9
22:18:47 CRITICAL - KI$+/̨̩,0" 400 -
22:18:47 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] code 400, message Bad HTTP/0.9 request type ('\x16\x03\x01\x02\x00\x01\x00\x01\xfc\x03\x03\x10\x91\x8ek\xf6\xf3_\xa3\x04ye\xc2V\xbeE+y\x93\x91WD\xc8\xef\xa2\xe8e\x90\x9c\xd1\xce\xc3\x94')
22:18:47 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] "k_yeVE+yWDeÔ j<\ٗ?us$+/̨̩,0" 400 -
22:18:47 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] code 400, message Bad request version ('6\xeb\xd7\xdd8^VTG\xa1=\xfc\xd35D\xd9"w\x87\x02\xa9\x86!\x1aT\x0e\x00$\x13\x01\x13\x03\x13\x02\xc0+\xc0/\xcc\xa9\xcc\xa8\xc0,\xc00\xc0')
22:18:47 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] "5C*[&ZbIU{ݛ: 
22:18:47 CRITICAL - 68^VTG=5D"w!T$+/̨̩,0" 400 -
22:18:47 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] code 400, message Bad request version ('\xfc\x8d\xbfSh\xe5\x18\x84\x94\xdb\xf0\x12\xe4\x80\xfc\x13\xee--\x1d\x00$\x13\x01\x13\x03\x13\x02\xc0+\xc0/\xcc\xa9\xcc\xa8\xc0,\xc00\xc0')
22:18:47 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] "Rt^+ܑ2}3lG"Ҝ|? -Gפv( Sh--
22:18:47 CRITICAL - $+/̨̩,0" 400 -
22:18:47 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] code 400, message Bad request syntax ('\x16\x03\x01\x02\x00\x01\x00\x01\xfc\x03\x03\xe6\xcb\x9b6qc\xe6\xa3\xed\x0e\x03\xac\x9d\xceT\x16\xbe9g\xe6\xbc\xdcl\xb8\x99\xa0\xa2\xe9\x0f\x82\x1fw @\x0b\xa6\xdcM\xb0\x969&47\xe3\x80N\xa2\xb8v\xaf\x16\xfc\xb8\x94\x00\xb8Q\xf1\x93|\x8b\r,\xa3\x00$\x13\x01\x13\x03\x13\x02\xc0+\xc0/\xcc\xa9\xcc\xa8\xc0,\xc00\xc0')
22:18:47 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] "˛6qcT9glw @
22:18:47 CRITICAL - M9&47NvQ|
22:18:47 CRITICAL - ,$+/̨̩,0" 400 -
22:18:47 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] code 400, message Bad request version ('\xa9\x00$\x13\x01\x13\x03\x13\x02\xc0+\xc0/\xcc\xa9\xcc\xa8\xc0,\xc00\xc0')
22:18:47 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] "ۓ?@T`IҬ1'
22:18:47 CRITICAL - ߉ 5rs
22:18:47 CRITICAL - c63}ݿ=ctA $+/̨̩,0" 400 -
22:18:47 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] code 400, message Bad request syntax ('\x16\x03\x01\x02\x00\x01\x00\x01\xfc\x03\x03\xc0\x94\xca;\x99\xf2L\xa8\xb7\xb3\xb0\xc5\xbd\xf5i\x0bI#<\xefK\x96\x0e\x18+O\xae!Q\x0cN\x8f \x1a\xaex\xb3L>\x8a2\xe9\x9cL\x11\xce\xc3,7\x80\xa3\xdf\xce\x19\xaf\xbd\xd5\x00O\xfd\x1eo{\xc9X\x00$\x13\x01\x13\x03\x13\x02\xc0+\xc0/\xcc\xa9\xcc\xa8\xc0,\xc00\xc0')
22:18:47 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] ";LŽi
22:18:47 CRITICAL - I#<K+O!Q
22:18:47 CRITICAL - N xL>2L,7O
22:18:47 CRITICAL - o{X$+/̨̩,0" 400 -
22:18:47 CRITICAL - 127.0.0.1 - - [05/Feb/2019 22:18:46] code 400, message Bad request syntax ('\x16\x03\x01\x02\x00\x01\x00\x01\xfc\x03\x03\x0c\xb7\x11\xd0\x88\xf5\xfc\x8c\x15WA\x19\xa2\x0c\xa68\x05_m\xcbz!\xa7\x06\xea\xd6\xe1\x9f\x7f:D\x1b f\x1d.\xfe\x86{w\x03\x18o\xb0\xc9kw\x1dUZ\xb9&\xf1k\x8c39#\xf9\xday\xf82v\x9{"thread": "ProcessReader", "process": "1112", "pid": 3712, "source": "web-platform-tests", "command": "C:\\tasks\\task_1549402762\\build\\application\\firefox\\firefox.exe -marionette about:blank --wait-for-browser -profile c:\\users\\testdr~1\\appdata\\local\\temp\\tmpmrvjla.mozrunner", "time": 1549405126943, "action": "process_output", "data": "[Child 2856: Main Thread]: I/signaling [main|PeerConnectionImpl] PeerConnectionImpl.cpp:2322: CloseInt: Closing PeerConnectionImpl f36e1bb17b08ddfa; ending call"}

I have seen these often while greening up windows v.1803 (build 17134); not sure if this is related to v.1803 or aarch64.

Hold for windows 10 1803 to go online.

Tested post-1803 update, bad HTTP errors still occur.

:jgraham - have you seen anything like this before? As far as I can tell, this is isolated to windows10-aarch64.

Flags: needinfo?(james)
Summary: web-platform-test | bad HTTP request errors → windows/aarch64 - web-platform-test | bad HTTP request errors

I think this happens on Windows-x86 as well i.e. it's not something related to aarch64.

What's happening (probably) is that a test is trying to make a non-HTTP request to a HTTP (not HTTPS) server. Looking at mozilla-central[1] I see this is a WebRTC test that's failing so I guess it's either https-to-http or somehow we're sending WebRTC data to a http server. I think the right thing would be for the WebRTC team to look at what's going on in this test.

[1] https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=232091866&repo=mozilla-central&lineNumber=11885

Flags: needinfo?(james) → needinfo?(drno)

I have not observed this failure in the last two weeks for windows10-aarch64.

Propose closing this bug as WORKSFORME now. If it re-emerges in the future we can file a bug then.

Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(drno)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.