| Summary: | [ iOS ] 2 imported/w3c/web-platform-tests/content-security-policy/connect-src/* tests are flaky text failures | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Dawn Morningstar <Morningstar> |
| Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW --- | ||
| Severity: | Normal | CC: | beidson, bfulgham, cdumez, pgriffis, webkit-bot-watchers-bugzilla, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
|
Description
Dawn Morningstar
2022-03-08 06:36:29 PST
marking expectations until further investigation can occur. Based on commits that landed shortly before the first failure, https://commits.webkit.org/247042@main seems like it could be related as it was about the SharedWorker process on iOS. (In reply to Ryan Haddad from comment #4) > Based on commits that landed shortly before the first failure, > https://commits.webkit.org/247042@main seems like it could be related as it > was about the SharedWorker process on iOS. Flaky timeouts could indeed indicate that we're failing to take a process assertion on iOS. I can investigate. (In reply to Chris Dumez from comment #5) > (In reply to Ryan Haddad from comment #4) > > Based on commits that landed shortly before the first failure, > > https://commits.webkit.org/247042@main seems like it could be related as it > > was about the SharedWorker process on iOS. > > Flaky timeouts could indeed indicate that we're failing to take a process > assertion on iOS. I can investigate. I haven't been able to reproduce so far, even by forcing the shared worker into its own separate process (which is more likely to trigger process suspension). |