Bug 6950 - bitbake errors must have unique ids to make them easily greppable in the source
Summary: bitbake errors must have unique ids to make them easily greppable in the source
Status: RESOLVED WONTFIX
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 1.8
Hardware: x86 Multiple
: Low enhancement
Target Milestone: Future
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-11-10 18:05 UTC by Alexandru Damian
Modified: 2017-09-14 15:30 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandru Damian 2014-11-10 18:05:04 UTC
Bitbake error must be prefixed with a unique ID, for each error, in the form "BBxyyyy" where "x" is a error severity indicator ("E", "W", "I" or "D" for Error, Warning, Info or Debug) and "yyyy" is a numeric ID starting with 0001.

E.g. instead of:
"Only one copy of bitbake should be run against a build directory"

bitbake output should be 

"BBE0001: Only one copy of bitbake should be run against a build directory"

Having unique textual IDs for errors make grepping through the source a lot easier, to allow for easy reference of code without having to hardcode locations.

E.g. a web interface could display relevant sections of code based on the error unique id by grepping through the source.
Comment 1 Richard Purdie 2014-11-13 15:41:20 UTC
This is a pretty invasive change which also has maintenance implications. At the very least this needs to be raised nd discussed with the community before we go any further with it. Alternatives such as the linenumber and file information should also be considered.
Comment 2 Richard Purdie 2017-09-14 15:30:56 UTC
We're not planning to do this right now, most errors can be found comparitively easily as the strings alone are fairly unique.