Bug 146697 – [Windows] LayoutTests/http/tests/security/contentSecurityPolicy/userAgentShadowDOM/allow-audio.html fails

• Status: RESOLVED
• Resolution: INVALID
• Component: Tools / Tests

[Daniel Bates]

The test LayoutTests/http/tests/security/contentSecurityPolicy/userAgentShadowDOM/allow-audio.html fails on Windows with diff:
[[
--- /home/buildbot/slave/win-release-tests/build/layout-test-results/http/tests/security/contentSecurityPolicy/userAgentShadowDOM/allow-audio-expected.txt
+++ /home/buildbot/slave/win-release-tests/build/layout-test-results/http/tests/security/contentSecurityPolicy/userAgentShadowDOM/allow-audio-actual.txt
@@ -1,4 +1,4 @@
 Tests that a HTML audio element, in a user agent shadow tree, is allowed to load when the page has CSP policy: media-src 'none'.
 
-PASS did load audio metadata.
+FAIL did not load audio metadata.
]]
<https://build.webkit.org/results/Apple%20Win%207%20Release%20(Tests)/r186414%20(52833)/http/tests/security/contentSecurityPolicy/userAgentShadowDOM/allow-audio-diff.txt>

See <https://build.webkit.org/results/Apple%20Win%207%20Release%20(Tests)/r186414%20(52833)/results.html>

[Daniel Bates]

The test was skipped in <http://trac.webkit.org/changeset/186447>.

[Daniel Bates]

Created attachment 256326 [details]
[Patch] Speculative patch

[Brent Fulgham]

Comment on attachment 256326 [details]
[Patch] Speculative patch

View in context: https://bugs.webkit.org/attachment.cgi?id=256326&action=review

> LayoutTests/http/tests/security/contentSecurityPolicy/userAgentShadowDOM/allow-audio.html:39
> +    audio.src = "resources/crow.wav";

Amazingly, WAV files won't work on Windows (at least, not Apple Windows) because we don't support WAV file decoding. Can you use an MP3 or something similar?

[Brent Fulgham]

The actual problem here is that "internals.ensureUserAgentShadowRoot" is not defined on Windows, at least for the element being queried. I'm debugging this now.

[Brent Fulgham]

The original AIF-based test runs fine locally on Release and Debug builds. So I think the test failure is purely a test machine configuration issue, and this patch is not necessary.