3a21698c

By: Tom Sydney Kerckhove <syd@cs-syd.eu>

Give the long diff timing test a timeout above its own bound

The test bounds the inner run at 120s, deliberately generously, so that
it fails only if the 2s diff timeout stopped working.  The default test
timeout is 60s, though, so on a machine slow enough for the bound to
matter the suite killed the test before its own timeout could decide
anything: it failed with Timeout! after ~65s in the nix sandbox, in two
of three runs, while printing the two 100k-element lists.

Raise the timeout for this one test above the bound it asserts, so the
bound is what decides the outcome.

Suite timing

Time to Start Worker time Duration Time to finish Idle
Config 0s 0s 0s 1s 0s
Eval 1s 33s 33s 34s 0s
Build 33s 1m42s 1m23s 1m57s 0s
Suite 0s 2m17s 1m57s 1m57s 0s

Timeline

0s10s20s30s40s50s1m1m10s1m20s1m30s1m40s1m50s