1774607 - Verify if some tests really cannot run with condprof active.

Status: NEW

(Core :: DOM: Service Workers, task)

Description

[Jens Stutte [:jstutte]]

Namely:

• test_https_fetch.html
• test_https_origin_after_redirect_cached.html
• test_openwindow.html

Comment 1

[Andrew Sutherland [:asuth] (he/him)]

With the fixes from https://phabricator.services.mozilla.com/D146317 as part of bug 1769110 that changed the specialized mochitest logic to fail a test if it leaves a serviceworker around to be okay with YouTube serviceworkers my local results are:

(In reply to Jens Stutte [:jstutte] from comment #0)

• test_https_fetch.html

Passes.

• test_https_origin_after_redirect_cached.html

Hangs with the conditioned profile, passes without it. For the conditioned profile, a popup window with the URL https://example.com/tests/dom/serviceworkers/test/fetch/origin/https/index-cached-https.sjs displays a 404. Reloading does not make the 404 go away. It's not clear what's up with that.

• test_openwindow.html

It is necessary to change the line tags = openwindow for this test to tags = condprof openwindow in order to run this test with --conditioned-profile because the tags directive clobbers the tags = condprof at the top of the test file and the test must be opted into condprof to be run.

Once that's done, the test hangs. It's hard to easily tell what's going on because the test checks 10 conditions in parallel and has no mechanism in place to provide any context if any of the promises fail to resolve or uniquely identifying characteristics in its ok() calls (although the ones with URLs are somewhat inherently self-identifying).