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.

Total

33s

Created Started Finished

Time to Start Worker time Duration Time to finish Idle
Config 0s 2s 2s 2s 0s
Eval 2s 12s 12s 15s 0s
Build 13s 0s 0s 13s 0s
Deploy 20s 13s 13s 33s 5s
Suite 0s 28s 33s 33s 5s

Timeline

Config Eval Build Deploy Compressed gap
0s10s30s