Bug 1143 - Remove python stack trace when do_patch fails
Summary: Remove python stack trace when do_patch fails
Status: RESOLVED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 1.0
Hardware: x86 Multiple
: Low enhancement
Target Milestone: 1.2 M3
Assignee: Paul Eggleton
QA Contact:
URL:
Whiteboard: (P1) (QA Testing Completed) Patch mer...
Depends on:
Blocks: 1543
  Show dependency tree
 
Reported: 2011-06-06 13:44 UTC by Scott Garman
Modified: 2012-02-05 07:44 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

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 Scott Garman 2011-06-06 13:44:46 UTC 
Marin Jansa noted that when do_patch fails during a build, the stack trace is enormous and unnecessary:

"A simple message that patch_do_patch failed because patch wasn't found or didn't apply without python trace would be much better."
Comment 1 Paul Eggleton 2012-01-19 07:55:34 UTC 
Fix merged in revision 11e5d7bc814a265d338dbb06d82e7533c2187be2.
Comment 2 Jiajun Xu 2012-02-05 07:44:11 UTC 
I tested with latest master commit cb89d43473a91ff4cb2447d642fcd9308d7366e3, the feature could work.