Bug 6391 - bitbake fails to warn of mkubifs error
Summary: bitbake fails to warn of mkubifs error
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.7
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.7
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-06-02 14:24 UTC by mark.roszko
Modified: 2014-06-06 10:36 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mark.roszko 2014-06-02 14:24:45 UTC 
I had my machine config set to have a LEB count that was too low for mkubifs to succeed by using MKUBIFS_ARGS. The expected behavior is bitbake would forward the error. Instead bitbake completes image building with as a success with 0 warnings and 0 errors. The images deploy directory ends up containing the intermediate ubifs but not the ubi image.

Running the intermediate script create_image.ubi in the image tmp folder ends up revealing the error message:

Error: max_leb_cnt too low (2211 needed)

This message was never handled by bitbake.

Reproduction is setting your machine conf with a 
MKUBIFS_ARGS = "(MACHINE dependent cruff) -c 600"
where the -c arg is a low number for your output build
and of course having one of the IMAGE_FSTYPES as ubi
Comment 1 Richard Purdie 2014-06-03 12:58:55 UTC 
I've sent out a patch which I believe will fix this issue.