New issue
Advanced search Search tips

Issue 903795 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression

Blocking:
issue 872776



Sign in to add a comment

http/tests/priorities/resource-load-priorities-service-worker.https.html fails on win10

Project Member Reported by cwallez@chromium.org, Nov 9

Issue description

This test was added in https://chromium-review.googlesource.com/c/chromium/src/+/1316104 and makes the win7_chromium_rel_ng that run the webkit layout tests very flaky. See https://ci.chromium.org/p/chromium/builders/luci.chromium.try/win7_chromium_rel_ng?limit=200

The error is caused by an INFO line being printed when on Windows before 8 (which makes sense since it is a Win7 builder):

04:49:21.304 5188 worker/1 http/tests/priorities/resource-load-priorities-service-worker.https.html output stderr lines:
04:49:21.304 5188   [6148:5400:1109/044920.276:INFO:media_foundation_video_encode_accelerator_win.cc(347)] Windows versions earlier than 8 are not supported.
 
Summary: http/tests/priorities/resource-load-priorities-service-worker.https.html fails on win10 (was: http/tests/priorities/resource-load-priorities-service-worker.https.html flaky on win7_chromium_rel_ng)
Changing the summary to indicate that the observed failures here are a red herring, and the actual cause was the fact that the internals.getResourcePriority API, from within a Service Worker, is always failing to return a proper resource priority on Win try bots.

Sign in to add a comment