1438796 - Re-Enable test_ext_contentscript_triggeringPrincipal.js on Windows Debug

Status: RESOLVED FIXED

(Core :: DOM: Security, enhancement, P3)

Comment 1

[Christoph Kerschbaumer [:ckerschb]]

Kris, do you have any suggestions what might be wrong with the test on windows debug? I tried to increase the timeout, but it still didn't work. If you have any insights, please let me know. thanks!

Comment 2

[Hsin-Yi Tsai (she/her) | away [:hsinyi]]

Let me know if you need more help from DOM Core team.

Comment 3

[Rob Wu [:robwu]]

Attachment: Bug 1438796 - Work around httpd deadlock in test_ext_contentscript_triggeringPrincipal.js

As mentioned in bug 1408193, the test interaction with httpd results in
a deadlock, which causes the test to fail intermittently. I observed
this test failure consistently on debug builds.

This patch works around the issue by replacing the use of httpd with a
webRequest.onBeforeRequest listener to extract the relevant request body
from the request.

Along with that, fixes an issue in the ExtensionTestUtils test utility;
it modifies the input manifest, but because the test reuses the
EXTENSION_DATA input between test tasks, the special behavior of merging
host_permissions with permissions for MV2 causes a test failure in the
MV3 test (because in MV3, permissions may not contain host permissions).

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/c4da70ccf221
Work around httpd deadlock in test_ext_contentscript_triggeringPrincipal.js r=zombie

Comment 5

[Sandor Molnar[:smolnar]]

https://hg.mozilla.org/mozilla-central/rev/c4da70ccf221

Comment 6

[Rob Wu [:robwu]]

FYI: Re-enabling the test exposed a pre-existing issue at bug 1940852.