Skip to content

Conversation

@jonahwilliams
Copy link
Contributor

Description

These are confusing when there is a compilation error, as it seems like the tool has failed.

Fixes #44963

@fluttergithubbot fluttergithubbot added the tool Affects the "flutter" command-line tool. See also t: labels. label Nov 15, 2019
@jonahwilliams
Copy link
Contributor Author

@dramosv90 I don't mind you leaving feedback or asking questions on PRs, but please don't leave empty approvals

if (!result.success) {
for (MapEntry<String, ExceptionMeasurement> data in result.exceptions.entries) {
printError('Target ${data.key} failed: ${data.value.exception}', stackTrace: data.value.stackTrace);
printError('Target ${data.key} failed: ${data.value.exception}');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two comments:

  • I'm seeing a few other potentially similar cases in aot.dart, bundle.dart, and web/compile.dart.
  • Is there any way that an ExceptionMeasurement can indicate whether the stack trace should be printed?

@jonahwilliams jonahwilliams merged commit a7367b6 into flutter:master Nov 18, 2019
@jonahwilliams jonahwilliams deleted the remove_context branch November 18, 2019 22:09
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

tool Affects the "flutter" command-line tool. See also t: labels.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Compiler error on flutter run causes tool to crash

5 participants