We've seen issues where diffs with comically large amounts test
failures can cause the diff to time out when loading. Part of the
issue appears to be that a new PhabricatorMarkupEngine is created
to render each test (which presumably prevents any cache hits?).
This diff just creates a single PhabricatorMarkupEngine and uses
that to marup all the result output from all tests.