Skip to content

Conversation

@compnerd
Copy link
Member

Rather than trying to silently continue, catch an execution error and report it to the user. There is no possible recovery at this point.

Rather than trying to silently continue, catch an execution error and
report it to the user. There is no possible recovery at this point.
@compnerd
Copy link
Member Author

@swift-ci please smoke test

endif()
execute_process(COMMAND ${module_triple_command} OUTPUT_VARIABLE target_info_json)
execute_process(COMMAND ${module_triple_command}
OUTPUT_VARIABLE target_info_json
Copy link
Member

Choose a reason for hiding this comment

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

While we're improving the failure path, can we also get the ERROR_VARIABLE and output what the error was, either in the CONFIGURE_LOG or as part of the fatal error if it exists.

execute_process(COMMAND ${module_triple_command} OUTPUT_VARIABLE target_info_json)
execute_process(COMMAND ${module_triple_command}
OUTPUT_VARIABLE target_info_json
RESULT_VARIABLE lastexitcode)
Copy link
Member

Choose a reason for hiding this comment

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

nit, but not a huge fan of carcrashcase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants