Bug 5663 - Hard to debug failing intercepts
Summary: Hard to debug failing intercepts
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.5
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 1.6
Assignee: Laurentiu Palcu
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-12-12 17:54 UTC by Ross Burton
Modified: 2014-02-14 14:55 UTC (History)
3 users (show)

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

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 Ross Burton 2013-12-12 17:54:57 UTC 
My rootfs is failing to run intercepts:

WARNING: intercept script "update_font_cache" failed, falling back to running postinstalls at first boot
  * postponing liberation-fonts
> Executing update_icon_cache
> Executing update_pixbuf_cache
WARNING: intercept script "update_pixbuf_cache" failed, falling back to running postinstalls at first boot

That's not very useful for debugging as I can't see what the problem is.  Is something being redirected to /dev/null or is there another log I can read?
Comment 1 Laurentiu Palcu 2013-12-13 07:43:50 UTC 
I'm currently working on rootfs/image creation refactoring and running intercepts will most likely be re-written in python. So, hopefully, will have a better way to debug intercepts.
Comment 2 Saul Wold 2013-12-19 15:35:33 UTC 
Please ensure you revisit this after you complete the refactoring
Comment 3 Laurentiu Palcu 2014-02-14 14:55:20 UTC 
After refactoring the rootfs code, warnings are printed directly to stdout if intercepts fail and the errors can be found in the log since they are not redirected to /dev/null anymore.