init_timeout should be higher when used with a debugger

[cbiesinger]

In wptrunner/browsers/base.py:

wpt/tools/wptrunner/wptrunner/browsers/base.py

Line 104 in f810dce

init_timeout: float = 30

However, I find that 30 is not enough when using wptrunner with rr. I am not sure if the right fix is to just increase the timeout, or apply timeout_multiplier to it, or something else, but I would appreciate a way to increase it.

Similarly:

wpt/tools/wptrunner/wptrunner/browsers/base.py

Line 397 in f810dce

kill_result = proc.kill(timeout=5)

When the test is timing out, I have found that 5 seconds is not sufficient for rr to finish writing/closing the trace so the same comment applies here.

[jcscottiii]

Note: I'm assuming this would be for Chrome testing.

Increase init_timeout value

Applying a timeout multiplier is something we could do. This is something that Firefox does too. This is done by supplying its own get_timeout_multiplier

Adjusting timeout for proc.kill

We might need some minor changes but we could leverage the browser specific get_timeout_multiplier in that same file.

[cbiesinger]

Yes I personally ran into this with Chrome. The file is not browser-specific so I thought this would be a general fix, but it seems the firefox driver overrides it so I guess that works too.