Re: [RFC] build to toaster fixes

[Michael Wood <michael.g.wood@intel.com>]

New branch: michaelw/toaster/ic-4-and-buildinfo-matching

This is based ontop of the image customisation branch to make sure we 
use the latest schema

Michael

On 20/09/15 23:39, Brian Avery wrote:
> Hi,
>
> I tried this branch on master and it worked fine for a
> core-image-minimal.  Could you give an example of what used to fail
> that this fixes?  I tried it with sujith's local layer loading and
> (for me) that still spews out ton's of errors about :
>
> Cannot determine the vcs_reference for layer version {'build_id': 2,
> '_layer_cache': <Layer: __FIXME__unidentified_layer / None >,
> 'layer_id': 10, '_state': <django.db.models.base.ModelState object at
> 0x7fd03ed98710>, 'up_branch_id': None, 'priority': 7, 'up_date': None,
> 'local_path': u'/', '_up_branch_cache': None, '_build_cache': <Build:
> 2 p1-suj (Release local (HEAD), BBV HEAD (Branch: HEAD))
> core-image-minimal>, 'branch': u'', 'dirpath': None, 'commit': u'',
> 'project_id': None, 'up_id': None, 'id': 28, 'layer_source_id': None},
> Project p1-suj (Release local (HEAD), BBV HEAD (Branch: HEAD)))>,
> <Layer_Version: 28 __FIXME__unidentified_layer / None  (VCS Cannot
> determine the vcs_reference for layer version {'build_id': 2,
> '_layer_cache': <Layer: __FIXME__unidentified_layer / None >,
> 'layer_id': 10, '_state': <django.db.models.base.ModelState object at
> 0x7fd03ed60d90>, 'up_branch_id': None, 'priority': 7, 'up_date': None,
> 'local_path': u'/', '_up_branch_cache': None, '_build_cache': <Build:
> 2 p1-suj (Release local (HEAD), BBV HEAD (Branch: HEAD))
> core-image-minimal>, 'branch': u'', 'dirpath': None, 'commit': u'',
> 'project_
>
>
> so, sadly this patch doesn't fix that problem :(
>
> -b
>
> On Fri, Sep 18, 2015 at 12:01 PM, Michael Wood <michael.g.wood@intel.com> wrote:
>> I've been working on a number of fixes to make sure that the build and layer
>> information is stored correctly in toaster.
>>
>> There is quite a bit of stuff needed to fix this more fully and definitely
>> scope for refactoring - I've left in old code paths as I don't think the
>> full extent of how the information is handled can be fully tested without a
>> large suite of unit tests.
>>
>> Branch is at 'michaelw/toaster/build-recognition-fixes' on poky-contrib.
>> I've had good results in testing building core-image-* on the fido release.
>>
>> Michael
>> --
>> _______________________________________________
>> toaster mailing list
>> toaster@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/toaster