New issue
Advanced search Search tips

Issue 686057 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

external/wpt/html/webappapis/system-state-and-capabilities/the-navigator-object/NavigatorID.html depends on unimported XMLHttpRequest/

Project Member Reported by kjellander@chromium.org, Jan 27 2017

Issue description

At least one of the Mac bots fail on: external/wpt/html/webappapis/system-state-and-capabilities/the-navigator-object/NavigatorID.html

It seems to have started with this build: https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Mac10.10/builds/29371
and only affects Mac 10.10.

Most likely it is caused by the new wpt import in https://chromium.googlesource.com/chromium/src/+/e8c75f95e39c0cc7cb1a0079abdad0a26e1abe0a

Log snippet:
05:02:14.991 11499 worker/7 external/wpt/html/webappapis/system-state-and-capabilities/the-navigator-object/NavigatorID.html output stderr lines:
05:02:14.991 11499   [05:02:14.601] vtDecompressionDuctCreate signalled err=-8973 (err) (Could not select and open decoder instance) at /SourceCache/CoreMedia_frameworks/CoreMedia-1562.235/Sources/VideoToolbox/VTDecompressionSession.c line 1181
05:02:14.991 11499   <<<< VTVideoEncoderSelection >>>> VTSelectAndCreateVideoEncoderInstanceInternal: no video encoder found for 'avc1'
05:02:14.991 11499   
05:02:14.991 11499   [05:02:14.677] VTSelectAndCreateVideoEncoderInstanceInternal signalled err=-12908 (err) (Video encoder not available) at /SourceCache/CoreMedia_frameworks/CoreMedia-1562.235/Sources/VideoToolbox/VTVideoEncoderSelection.c line 1245
05:02:14.991 11499   [05:02:14.677] VTCompressionSessionCreate signalled err=-12908 (err) (Could not select and open encoder instance) at /SourceCache/CoreMedia_frameworks/CoreMedia-1562.235/Sources/VideoToolbox/VTCompressionSession.c line 946
05:02:14.991 11499   <<<< VTVideoEncoderSelection >>>> VTSelectAndCreateVideoEncoderInstanceInternal: no video encoder found for 'avc1'
05:02:14.991 11499   
05:02:14.991 11499   [05:02:14.677] VTSelectAndCreateVideoEncoderInstanceInternal signalled err=-12908 (err) (Video encoder not available) at /SourceCache/CoreMedia_frameworks/CoreMedia-1562.235/Sources/VideoToolbox/VTVideoEncoderSelection.c line 1245
05:02:14.991 11499   [05:02:14.677] VTCompressionSessionCreate signalled err=-12908 (err) (Could not select and open encoder instance) at /SourceCache/CoreMedia_frameworks/CoreMedia-1562.235/Sources/VideoToolbox/VTCompressionSession.c line 946
05:02:14.996 6070 [5/23] external/wpt/html/webappapis/system-state-and-capabilities/the-navigator-object/NavigatorID.html failed unexpectedly (text diff)
05:02:14.994 11499 worker/7 external/wpt/html/webappapis/system-state-and-capabilities/the-navigator-object/NavigatorID.html failed:
05:02:14.994 11499 worker/7  text diff
05:02:14.995 11499 worker/7 killing secondary driver
 
Project Member

Comment 1 by bugdroid1@chromium.org, Jan 27 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/0db58634865bb99accfe011eb7fcc313476f615e

commit 0db58634865bb99accfe011eb7fcc313476f615e
Author: kjellander <kjellander@chromium.org>
Date: Fri Jan 27 13:40:51 2017

Update expectations for external/wpt/html/webappapis/system-state-and-capabilities/the-navigator-object/NavigatorID.html

BUG= 686057 
TBR=qyearsley@chromium.org
NOTRY=True

Review-Url: https://codereview.chromium.org/2664443003
Cr-Commit-Position: refs/heads/master@{#446659}

[modify] https://crrev.com/0db58634865bb99accfe011eb7fcc313476f615e/third_party/WebKit/LayoutTests/TestExpectations

Cc: tkent@chromium.org
Components: Blink>Infra
Here, the specific mismatch was caused by the fact that the expected baseline included the string "Mac OS X 10_10_5" and the actual result included the string "Mac OS X 10_10_4".

So, this test, as-is, will have different results whenever the specific sub-version of the OS changes.

It's possible that something about the way the test is run with run-webkit-tests makes it fail right now, since this test is passing for me when I try it directly: http://w3c-test.org/html/webappapis/system-state-and-capabilities/the-navigator-object/NavigatorID.html

This test may be failing now because when this test is run with run-webkit-tests, there's an XHR that doesn't return what it is expected to return (see this part of the test: https://github.com/w3c/web-platform-tests/blob/master/html/webappapis/system-state-and-capabilities/the-navigator-object/NavigatorID.js#L58)

Fail message:

FAIL userAgent value assert_equals: userAgent should return the value sent in the User-Agent header expected "{\"error\": {\"message\": \"\", \"code\": 404}}" but got "user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.77.34.5 Safari/537.36\n"

See:
http://w3c-test.org/html/webappapis/system-state-and-capabilities/the-navigator-object/NavigatorID.html
http://w3c-test.org/XMLHttpRequest/resources/inspect-headers.py?filter_name=User-Agent

Comment 3 by tkent@chromium.org, Jan 30 2017

NavigatorID.js:
    request.open("GET", "/XMLHttpRequest/resources/inspect-headers.py?" +
                        "filter_name=User-Agent");

We don't import web-platform-tests/XMLHttpRequest yet.


Comment 4 by tkent@chromium.org, Feb 15 2017

Cc: qyears...@chromium.org
Components: -Blink>Infra Blink>Network>XHR Blink>HTML
Labels: -Pri-2 Pri-3
Owner: ----
Status: Available (was: Assigned)
Summary: external/wpt/html/webappapis/system-state-and-capabilities/the-navigator-object/NavigatorID.html depends on unimported XMLHttpRequest/ (was: external/wpt/html/webappapis/system-state-and-capabilities/the-navigator-object/NavigatorID.html flaky on Mac)
Project Member

Comment 5 by sheriffbot@chromium.org, Feb 15 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by tkent@chromium.org, Feb 16 2018

Status: WontFix (was: Untriaged)
The test doesn't exist even in the upstream.

Sign in to add a comment