recipes: print recipe ENV on failure #2403
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AndreMiras
approved these changes
Jan 7, 2021
There was a problem hiding this comment.
LGTM, I wish we took the opportunity to increase test coverage of this module slightly.
See tests/test_logger.py if you're motivated 😃
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Print contents of
_envwhen recipe fails andP4A_FULL_DEBUGis set. Printedexportcommands allow for recreation of recipe's build enviroment and faster iteration when developing complex recipes. This acts as a poor man's substitute for the analogous devshell feature in OpenEmbedded.