-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lmp/bb-build: clarify the bitbake notification #356
base: master
Are you sure you want to change the base?
Conversation
eb17bd3
to
1e95509
Compare
I think I understand the goal of the PR. It is only to add a log line to the end of bitbake execution, not to specify where the error is. In the PR/commit log it's "bitbake finish" and in the source code it's "bitbake done" |
right
what I wanted to notify with these steps was the following:
maybe I could use other words for this instead of having finish/rsync/done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Nice improvement, I personally was confused some times by such error message at the end of the log :)
I don't know either. I think finish and done is misleading out of context what about
|
- add notification about the end - change the finish notification to post processing When there are errors during the bitbake build it is always necessary to perform some additional post-processing steps such as: == Run bitbake (finish) == Run bitbake (rsync factory sstate-cache mirror) Script completed with error(s) Only after this last step is reported that there was an error. This leads the user to think that the error was in the last step, in this case the rsync, which is not true. Example: Summary: 1 task failed: /srv/oe/build/conf/../../layers/meta-subscriber-overrides/recipes-samples/images/lmp-factory-image.bb:do_image_garagecheck Summary: There were 4 WARNING messages. Summary: There was 1 ERROR message, returning a non-zero exit code. == 2024-10-10 12:00:20 Run bitbake (finish) bootchart written to '/archive/bitbake_buildchart.svg' == 2024-10-10 12:00:24 Run bitbake (rsync factory sstate-cache mirror) Script completed with error(s) == 2024-10-10 12:01:32.828429: Finding artifacts to upload Uploading 14 items 53779607 bytes == 2024-10-10 12:01:36.053422: Runner has completed ________ | o o| Thumbs Down |___/\_|________ | _____|__| | | || |______| | | | | | | | | |_| |_| Signed-off-by: Jose Quaresma <[email protected]>
1e95509
to
ee2fddf
Compare
done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
When there are errors during the bitbake build it is always necessary to perform some additional post-processing steps such as:
== Run bitbake (finish)
== Run bitbake (rsync factory sstate-cache mirror)
Script completed with error(s)
Only after this last step is reported that there was an error. This leads the user to think that the error was in the last step, in this case the rsync, which is not true.
Example: