feature-policy/reporting/* tests are almost all expected fail || timeout
Categories
(Core :: DOM: Security, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox78 | --- | fixed |
People
(Reporter: jmaher, Assigned: baku)
References
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
I see that almost all of the tests in feature-policy/reporting are expected fail or timeout:
https://searchfox.org/mozilla-central/source/testing/web-platform/meta/feature-policy/reporting
and the tests:
https://searchfox.org/mozilla-central/source/testing/web-platform/tests/feature-policy/reporting
there are two types of tests:
reporting
report-only
typicaly report-only is timeout and in 8 cases reporting runs successfully (for example in the case of camera)
for the tests that timeout we are getting no value and wasting time waiting for results and cpu/money.
I would like to determine why these are failing and get them passing quickly.
Reporter | ||
Comment 1•5 years ago
|
||
:hsinyi, I see you as the triage owner, can you help determine if we support what these tests are testing for and if so why they are failing? Maybe you can redirect to the appropriate engineer.
Reporter | ||
Updated•5 years ago
|
Comment 2•5 years ago
|
||
Hi Christoph, could you please help me to answer Joel's question? Also, I've been thinking about update the in-tree metadata of feature-policy to ensure the related test bugs are filed under DOM: Security. What do you think about this idea? Thank you.
Comment 3•5 years ago
|
||
(In reply to Hsin-Yi Tsai [:hsinyi] from comment #2)
Hi Christoph, could you please help me to answer Joel's question? Also, I've been thinking about update the in-tree metadata of feature-policy to ensure the related test bugs are filed under DOM: Security. What do you think about this idea? Thank you.
@ Hsin-Yi: I think it makes sense to update the in-tree metadata so that feature-policy bugs are filed in Dom:Security.
@Johann: You have a better overview of feature-policy, can you help advise how to move forward with: feature-policy/reporting tests?
Reporter | ||
Comment 4•5 years ago
|
||
when any fixes to the tests or manifests are done, we can update the in-tree component (:hsinyi has the right link in comment 2). I am happy to change manifests around if we find that this isn't supported. Hopefully it is the tests need updating or a pref is needed or something like that.
Updated•5 years ago
|
Reporter | ||
Comment 5•5 years ago
|
||
following up here, been 1+ week on needinfo.
Updated•5 years ago
|
Assignee | ||
Comment 6•5 years ago
|
||
Feature-Policy-Report-Only header is not supported. We need to disable all these tests. I'll send a patch.
Assignee | ||
Comment 7•5 years ago
|
||
Updated•5 years ago
|
Comment 9•5 years ago
|
||
bugherder |
Updated•4 years ago
|
Description
•