This error message makes sense in the context exactly how it's run in flutter/packages CI, where packages have already gone through analysis normally, but not in other cases like local usage or, importantly, flutter/flutter where we only run analysis with this form.

We should make the error message more generic, as a failure here can also just mean that there are resolution failures in general, and the current message caused confusion when that happened in flutter/flutter.