Bug 372

Summary: kernel: out of sync trees can cause opaque error messages when forcing branches
Product: [Yocto Project Subprojects] Kernel Reporter: Bruce Ashfield <bruce.ashfield>
Component: kernel-toolingAssignee: Bruce Ashfield <bruce.ashfield>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: Undecided CC: kevin.tian, sgw, yp.watcher
Version: unspecified   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Program Management Documentation change: ---

Description Bruce Ashfield 2010-09-30 07:38:29 UTC
If for some unknown reason, the kernel git repository hasn't been properly
updated and is *older* than the revisions listed in default-revisions the
branch sanity checking kicks in and tries to force branches to the right
revs. The problem is, the revisions it is looking for don't exist in the tree.
As a result, error messages are thrown about invalid commit IDs. These
aren't helpful, and are simply confusing for the user.

Instead we can test for the commit ID, and if it isn't valid, indicate
that the commit ID isn't valid and that the tree is potentially out
of sync.

This situation is not common, but it is an easy test and the extra
sanity checking is useful.
Comment 2 Bruce Ashfield 2010-12-13 05:56:17 UTC
Forced a tree to have a newer / impossible commit ID and a 
useful error message is produced.