When a timeout occurs in the shard split passthrough itself (and not one of the tests running) evergreen detects the task times out, but does not list any test as "failed". This creates a confusing situation. A solution could be for the passthrough to create a test for itself, which evergreen would list as "timed out"