How can I make "flutter drive" fail on a RenderFlex overflow exception?

I have a flutter drive integration test that will run tests on various devices as part of a CI build. Flutter drive only logs the exception in the output, but does not fail the test. Is there some way to force the test to fail when the rendering engine throws this Renderflex overflow exception?

$ flutter drive test_driver/app.dart

I/flutter (20477): ══╡ EXCEPTION CAUGHT BY RENDERING LIBRARY ╞═════════════════════════════════════════════════════════
I/flutter (20477): The following assertion was thrown during layout:
I/flutter (20477): A RenderFlex overflowed by 1.00 pixels on the bottom.
...
I/flutter (20477): ◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤
I/flutter (20477): ════════════════════════════════════════════════════════════════════════════════════════════════════
00:25 +4: MyTestDriver App (tearDownAll)
00:25 +4: All tests passed!

All searches turn up questions about how to fix the problem, but none about how to test for and detect it as part of an integration test in a CI build.

Ideally, the test would return non-zero and would let the CI system fail a commit that introduces a new rendering bug.