On my rpi2, the test was taking about 3m 40s before this change, and is now taking about 5m 14s, above the 240s (4 mins) timeout limit. I suspect this might be showing a wider performance regression.
This should be solved after https://trac.webkit.org/r238778. Could you confirm this?
(In reply to Caio Lima from comment #1) > This should be solved after https://trac.webkit.org/r238778. Could you > confirm this? Indeed! *** This bug has been marked as a duplicate of bug 192203 ***