After @bparrishMines recently discovered that we were silently not running webview_flutter integration tests for Android via FTL, I wanted to change the command to fail whenever an Android-supporting package doesn't run any tests, just as we now do with drive-examples for the same reason. I uploaded the draft PR to get the list of failing plugins to temporarily exclude and file an issue for, and was surprised that only one shard was failing.

On investigation, the other three shards have output that just ends abruptly. In each case it appears that it had previously run one test, and the last thing it has printed is the banner that indicates that it's about to run for another plugin. I checked, and those final plugins do have the test folders. Given that, my current theory is that somehow the script is aborting (but not exiting with a non-zero code somehow) when trying to run a second test.

/cc @bparrishMines @blasten I'm going to investigate, but FYI since it's relevant to current work.