Intermittent TEST-UNEXPECTED-TIMEOUT | /feature-policy/reporting/encrypted-media-report-only.https.html | Encrypted Media report only mode - Test timed out
Categories
(Core :: Audio/Video, defect, P5)
Tracking
()
People
(Reporter: intermittent-bug-filer, Unassigned)
Details
(Keywords: intermittent-failure, regression, Whiteboard: [stockwell unknown])
Attachments
(2 files)
Filed by: nbeleuzu [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=257528171&repo=mozilla-central
Full log: https://queue.taskcluster.net/v1/task/Fz1dwioOQNCImztCHr1mnw/runs/0/artifacts/public/logs/live_backing.log
14:49:17 INFO - TEST-START | /feature-policy/reporting/encrypted-media-report-only.https.html
14:49:17 INFO - Clearing pref dom.security.featurePolicy.enabled
14:49:17 INFO - Clearing pref dom.security.featurePolicy.webidl.enabled
14:49:17 INFO - Clearing pref dom.reporting.featurePolicy.enabled
14:49:17 INFO - Clearing pref dom.vr.enabled
14:49:17 INFO - Clearing pref dom.payments.request.enabled
14:49:17 INFO - Clearing pref dom.reporting.enabled
14:49:17 INFO - Clearing pref dom.security.featurePolicy.header.enabled
14:49:17 INFO - Clearing pref dom.webmidi.enabled
14:49:17 INFO - Setting pref dom.security.featurePolicy.enabled (true)
14:49:17 INFO - Setting pref dom.security.featurePolicy.webidl.enabled (true)
14:49:17 INFO - Setting pref dom.reporting.featurePolicy.enabled (true)
14:49:17 INFO - Setting pref dom.vr.enabled (true)
14:49:18 INFO - Setting pref dom.payments.request.enabled (true)
14:49:18 INFO - Setting pref dom.reporting.enabled (true)
14:49:18 INFO - Setting pref dom.security.featurePolicy.header.enabled (true)
14:49:18 INFO - Setting pref dom.webmidi.enabled (true)
14:49:18 INFO - Closing window 15032385537
14:49:18 INFO - PID 5716 | [Child 8360, Chrome_ChildThread] WARNING: pipe error: 109: file z:/task_1563608939/build/src/ipc/chromium/src/chrome/common/ipc_channel[Parent 7956, Gecko_IOThread] WARNING: pipe error: 109: file z:/task_1563608939/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 341
14:49:18 INFO - PID 5716 | [Child 3404, Chrome_ChildThread] WARNING: pipe error: 109: file z:/task_1563608939/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 341
14:49:58 INFO -
14:49:58 INFO - TEST-UNEXPECTED-TIMEOUT | /feature-policy/reporting/encrypted-media-report-only.https.html | Encrypted Media report only mode - Test timed out
14:49:58 INFO - TEST-INFO | expected FAIL
14:49:58 INFO - TEST-UNEXPECTED-TIMEOUT | /feature-policy/reporting/encrypted-media-report-only.https.html | expected OK
14:49:58 INFO - TEST-INFO took 41036ms
Comment hidden (Intermittent Failures Robot) |
Comment 2•6 years ago
|
||
Comment hidden (Intermittent Failures Robot) |
Updated•6 years ago
|
Comment 4•6 years ago
|
||
Comment 5•6 years ago
|
||
can you backfill on the merge and figure out which test caused the failure?
Comment 6•6 years ago
|
||
So far, I think https://bugzilla.mozilla.org/show_bug.cgi?id=1561774 caused the failures. I'm waiting for retriggers and will update the bug soon.
Comment 7•6 years ago
|
||
rmaries was right, this started after Bug 1561774 got landed:
https://treeherder.mozilla.org/#/jobs?repo=autoland&resultStatus=success%2Cpending%2Crunning%2Ctestfailed%2Cbusted%2Cexception&searchStr=windows%2C10%2Caarch64%2Copt%2Cweb%2Cplatform%2Ctests%2Ctest-windows10-aarch64%2Fopt-web-platform-tests-e10s-10%2Cw%28wpt10%29&revision=05ecec42602f0dad6bb97d631eeed7b3fd1812e1
mshal: Can you please take a look at this?
Comment 8•6 years ago
|
||
I'm not really sure what this test does -- jmaher, do you have any suggestions here? Or who else I could bug for help? :)
Before my patch, the tests ran on win64-aarch64/opt, and after my patch, they run on win64-aarch64-shippable/opt, which itself is comprised of win32-shippable/opt and win64-aarch64-shippable-no-eme/opt. So I guess previously it was using EME from the win64 build, and now it's failing with EME from the win32 part of the build?
I'm also a little confused by the test manifest, since the failing test shows:
INFO - TEST-UNEXPECTED-TIMEOUT | /feature-policy/reporting/encrypted-media-report-only.https.html | Encrypted Media report only mode - Test timed out
INFO - TEST-UNEXPECTED-TIMEOUT | /feature-policy/reporting/encrypted-media-report-only.https.html | expected OK
but the test manifest has:
[encrypted-media-report-only.https.html]
expected:
if (os == "android") and not e10s: OK
if (os == "win") and (processor == "aarch64"): OK
if (os == "android") and e10s: OK
TIMEOUT
[Encrypted Media report only mode]
expected:
if (os == "android") and not e10s: FAIL
if (os == "win") and (processor == "aarch64"): FAIL
if (os == "android") and e10s: FAIL
TIMEOUT
To me it looks like for the "Encrypted Media report only mode", we are expecting FAIL for win/aarch64, but the error message says it is expecting OK (and the previous build gets OK).
Comment 9•6 years ago
|
||
My understanding of eme and what we are doing for aarch64 is lacking. I don't understand what was running before in opt and now what is running in shippable. I assume whatever we build and test is what we ship and we should be able to support EME.
:ajones, do you know who could help answer this?
Comment hidden (Intermittent Failures Robot) |
Comment 11•6 years ago
|
||
Updated•6 years ago
|
Comment 12•6 years ago
|
||
bugherder |
Comment hidden (Intermittent Failures Robot) |
Comment 14•5 years ago
|
||
This bug failed 44 times in the last 7 days. Occurs on windows10-aarch64 on opt build types.
Recent log:
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=262198993&repo=mozilla-central&lineNumber=4873
Comment hidden (Intermittent Failures Robot) |
Comment 16•5 years ago
|
||
Comment 17•5 years ago
•
|
||
Try push for the patch I added.
Comment hidden (Intermittent Failures Robot) |
Comment 19•5 years ago
|
||
Comment 20•5 years ago
|
||
bugherder |
Comment hidden (Intermittent Failures Robot) |
Comment 22•5 years ago
|
||
dluca, anything you want to do here? Should we remove the leave-open
tag maybe ?
Updated•5 years ago
|
Comment 23•5 years ago
|
||
Paul: I only updated the expectation in that patch, I wouldn't say the bug is fixed because of that.
I don't think removing the tag would help the bug getting fixed.
Updated•2 years ago
|
Comment 24•4 months ago
|
||
https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.
Updated•4 months ago
|
Description
•