Bug 9949 - oe-selftest needs to verify bberror etc
Summary: oe-selftest needs to verify bberror etc
Status: RESOLVED FIXED
Alias: None
Product: Runtime Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: 2.1
Hardware: All Multiple
: Medium enhancement
Target Milestone: 4.99
Assignee: Apoorv
QA Contact: Apoorv
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-07-15 10:34 UTC by Ross Burton
Modified: 2019-10-04 07:39 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Burton 2016-07-15 10:34:51 UTC
Shell functions in bitbake get given functions and FIFOs so they can emit logs to the user (bberror, bbwarn, etc).

Since the Py3 migration these have been broken and nobody noticed until image generation failed without any messages.

We need a simple recipe to call bberror/bbwarn etc and verify that they are working as expected by grepping the cooker log after invoking bitbake.

github:rossburton/meta-ross/classes/crasher.bbclass is my local test class for experimenting with this. Note that it does a bbwarn after bbfatal so I can verify that bbfatal has in fact aborted.
Comment 1 Benjamin Esquivel 2016-07-15 17:22:38 UTC
assigning to José so he finds the right owner in QA.
Comment 2 Jose Perez C 2017-06-30 19:24:12 UTC
Patch on the list 

https://patchwork.openembedded.org/patch/141441/
Comment 3 Jose Perez C 2017-08-30 15:47:37 UTC
Moved to 2.5 due resources constraint
Comment 4 Jose Perez C 2017-08-30 15:48:26 UTC
Moved to 2.5 due resources constraint
Comment 5 Sangeeta Jain 2019-10-04 07:39:15 UTC
test bbtests.py is merged in selftests