There is something really odd here. All the tests seem to take 25 seconds to run after your patch: - move-back-iframe-parse-error-external-classic.html | took 24264ms - move-back-iframe-parse-error-external-module.html | took 24294ms - move-back-iframe-parse-error-inline-classic.html | took 24258ms - ... Whereas before your patch, they would only take 12 seconds: - move-back-iframe-fetch-error-external-classic.html | took 12314ms - ... Those tests don't seem to timeout, but they still take as much time as possible. Which makes the whole suite much longer. Maybe we are hitting some kind of global timeout because of this?
Bug 1774933 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
There is something really odd here. All the tests seem to take 25 seconds to run after your patch: - move-back-iframe-parse-error-external-classic.html | took 24264ms - move-back-iframe-parse-error-external-module.html | took 24294ms - move-back-iframe-parse-error-inline-classic.html | took 24258ms - ... Whereas before your patch, they would only take 12 seconds: - move-back-iframe-fetch-error-external-classic.html | took 12314ms - ... Those tests don't seem to timeout, but they still take as much time as possible. Which makes the whole suite much longer. Maybe we are hitting some kind of global timeout because of this? Edit: Those tests [seem to heavily rely on the "step_timeout" helper]( https://searchfox.org/mozilla-central/source/testing/web-platform/tests/html/semantics/scripting-1/the-script-element/moving-between-documents/resources/moving-between-documents-helper.js) which is [impacted by the timeout_multiplier](https://searchfox.org/mozilla-central/rev/a26af613a476fafe6c3eba05a81bef63dff3c9f1/testing/web-platform/tests/resources/testharness.js#2706-2712) we modified in the regressing bug.