Part of a solution would probably to fix the test to not call setTimeout directly, but instead call testharness' step_timeout, which will automatically apply the correct timeout multiplier to the timeout? That way the timeout would only need to actually be 10 seconds on slow platforms while fast platforms can get a faster timeout. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1194#issuecomment-329230799
Received on Wednesday, 13 September 2017 16:56:54 UTC