image_type_torizon: improve warning for non-versioned layers #207
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
Currently, the warning for non-versioned layers involved in a build is not much helpful: ``` WARNING: Failed to get layers information. Exception: <class 'bb.process.ExecutionError'> ``` With this commit, the message will point which layer is causing it and what is the specific error that happened. E.g.: ``` WARNING: Failed to get layers information. Caused by layer at /workdir/torizon-7/layers/meta-iotedge-torizon. Exception: Execution of 'export PSEUDO_UNLOAD=1; git rev-parse HEAD' failed with exit code 128: fatal: not a git repository (or any parent up to mount point /) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). ``` Signed-off-by: Henrique Garcia <[email protected]>
|
Hey @EdTheBearded can you review this contribution? |
EdTheBearded
approved these changes
Jan 16, 2025
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.
Currently, the warning for non-versioned layers involved in a build is not much helpful:
With this commit, the message will point which layer is causing it and what is the specific error that happened. E.g.: