Give the trim timing check room for a slow host

The about-render unit test bounds three renders at one second to catch
the cubic trim coming back. They take 0.1 s natively and three seconds
on an emulated x86_64 host, where the check failed, while the old code
took minutes, so ten seconds still tells the two apart.

0 files changed, 0 insertions, 0 deletions