Today I tried to land #62635

There were test failures:

The "details" link leads to this page. It's not clear what "Step('display builds.build(s) failed') (retcode: 1)" means, however one can try re-running the test from here.

Re-running the test didn't magically improve the situation, so I tried following the "View more details on flutter-dashboard" link. That link leads to a page packed full of a remarkable amount of information, most of which doesn't appear to be relevant to discovering what's gone wrong with the failed test. There are many links in likely red areas, but only the one indicated by the arrow, leads closer to information about the source of the test failure.

The destination page looks similar, and it includes another link in a likely red box (albeit under a rather opaque heading) which leads to the transcript from the failing test.

Having got this far, the failure is still hard to reason about:

02:45 +4675 ~13 -2: /b/s/w/ir/k/flutter/packages/flutter/test/rendering/viewport_test.dart: Nested viewports (same orientation) showOnScreen not in view of neither inner nor outer                    
02:45 +4675 ~13 -2: /b/s/w/ir/k/flutter/packages/flutter/test/rendering/reattach_test.dart: objects can be detached and re-attached: layout [E]                                                        
  'package:flutter/src/semantics/semantics.dart': Failed assertion: line 0: 'value != null': is not true.

It turns out that the people who have been working on this problem can tell you that it's been recently fixed and that it will likely go away if the PR is sync'd up and resubmitted.

So. The reason for going through all of this is to observe that it's difficult to discover what's gone wrong because it's difficult to navigate the reports we're providing. I'm coming at this from within Google and I have to assume that it's even more difficult to navigate for an external developer.

I hope we can find a way to make navigating these reports easier.