Bug 269086
| Summary: | [ iOS 17 Release ] imported/w3c/web-platform-tests/feature-policy/feature-policy-frame-policy-allowed-for-all.https.sub.html is a constant flaky text failure | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Jay Stfleur <j_stfleur> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | cdumez, webkit-bot-watchers-bugzilla, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Jay Stfleur
Description:
imported/w3c/web-platform-tests/feature-policy/feature-policy-frame-policy-allowed-for-all.https.sub.html
Is a flaky failure text failure
History:
https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Ffeature-policy%2Ffeature-policy-frame-policy-allowed-for-all.https.sub.html
Diff/Image Diff/Crash Log:
https://ews-build.s3-us-west-2.amazonaws.com/iOS-17-Simulator-WPT-WK2-Tests-EWS/43d8eb76-12932-clean-tree/imported/w3c/web-platform-tests/feature-policy/feature-policy-frame-policy-allowed-for-all.https.sub-pretty-diff.html
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/122661509>
Jay Stfleur
Reproducibility:
run-webkit-test --ios-simulator imported/w3c/web-platform-tests/feature-policy/feature-policy-frame-policy-allowed-for-all.https.sub.html --child-process=1 --iterations 50
EWS
Test gardening commit 274386@main (f01f55627f32): <https://commits.webkit.org/274386@main>
Reviewed commits have been landed. Closing PR #24172 and removing active labels.
Chris Dumez
The diff is about:
```
Blocked access to external URL https://www.localhost:9443/feature-policy/resources/feature-policy-allowedfeatures.html
Blocked access to external URL https://www.localhost:9443/feature-policy/resources/feature-policy-allowedfeatures.html
```
The test is not functional because it tries to load from the "https://www.localhost" domain. Sadly, our test infrastructure doesn't support such domains yet. We also don't currently have a way to silence the "Blocked access to external URL" messages it seems. As a result, marking the test as flaky is the right thing to do for now.
We should be able to re-enable once our test infrastructure gets updated to support custom localhost domains (which I believe Matthew is working on).