[OE-core] [PATCH V2 1/1] kernel.bbclass: Add kernel_version_sanity_check function

[Bruce Ashfield]

On Mon, Sep 19, 2016 at 6:02 PM, Cal Sullivan <
california.l.sullivan at intel.com> wrote:

> I don't have time to smoke test a SRCREV update for so many machines right
> now, so I think for now I will just set the correct PV in the various
> linux-yocto recipes so we don't block master-next builds.
>
> Is this acceptable?
>

In the linux-yocto bbappends of the various layers ? I keep track of the
PV's in the
core recipes themselves, so they shouldn't need to be modified.

Bruce


>
> Thanks,
> Cal
>
>
> On 09/19/2016 01:49 PM, Saul Wold wrote:
>
>> On Mon, 2016-09-19 at 15:55 -0400, Bruce Ashfield wrote:
>>
>>> On 2016-09-19 03:53 PM, Cal Sullivan wrote:
>>>
>>>> Yep, these all have incorrect PVs.
>>>> 628bf62756 Merge tag 'v4.4.11' into standard/base
>>>> The problem seems fairly wide spread.
>>>>
>>>> Bruce, do you suggest updating PVs or updating the SRCREVs (is
>>>> there a
>>>> good reason to keep using old SRCREVs?)?
>>>>
>>> Updating the SRCREVs is the right thing to do to sync them up now.
>>>
>>> but ..
>>>
>>> at the same time, they should probably have their own PVs, since
>>> next time up update 4.4.x, they'll fall out of sync and fail again.
>>>
>>> +1, I think that these need their own PV since they also don't update
>> as fast as the base qemu recipes do.
>>
>> Sau!
>>
>> We want them to be aligned with the latest -stable, but we also
>>> don't need failures every time I push a new SRCREV and update the
>>> PV of the base recipe.
>>>
>>> Bruce
>>>
>>>
>>>> ---
>>>> Cal
>>>>
>>>>
>>>> On 09/19/2016 11:54 AM, Burton, Ross wrote:
>>>>
>>>>>
>>>>> On 19 September 2016 at 18:05, Cal Sullivan
>>>>> <california.l.sullivan at intel.com
>>>>> <mailto:california.l.sullivan at intel.com>> wrote:
>>>>>
>>>>>      It looks like the function is doing as its supposed to, and
>>>>> we
>>>>>      need to update some PVs or SRCREVs to match PVs.
>>>>>
>>>>>      E.g., on the error below, SRCREV d6237b3b24 is indeed 4.1.31.
>>>>>
>>>>>
>>>>> And some more builders failed with 4.4:
>>>>>
>>>>> ERROR: linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0
>>>>> do_kernel_version_sanity_check: Package Version
>>>>> (4.4.20+gitAUTOINC+e66032e2d9_628bf62756) does not match of
>>>>> kernel
>>>>> being built (4.4.11). Please update the PV variable to match the
>>>>> kernel source.
>>>>> ERROR: linux-yocto-4.4.20+gitAUTOINC+e66032e2d9_628bf62756-r0
>>>>> do_kernel_version_sanity_check: Function failed:
>>>>> do_kernel_version_sanity_check (log file is located at
>>>>> /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-
>>>>> arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-
>>>>> yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-
>>>>> r0/temp/log.do_kernel_version_sanity_check.30210)
>>>>> NOTE: recipe usbutils-008-r0: task do_fetch: Started
>>>>> ERROR: Logfile of failure stored in:
>>>>> /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-
>>>>> arm/build/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-
>>>>> yocto/4.4.20+gitAUTOINC+e66032e2d9_628bf62756-
>>>>> r0/temp/log.do_kernel_version_sanity_check.30210
>>>>> ERROR: Task
>>>>> (/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-
>>>>> arm/build/meta/recipes-kernel/linux/linux-
>>>>> yocto_4.4.bb:do_kernel_version_sanity_check)
>>>>> failed with exit code '1'
>>>>>
>>>>> (ditto for ppc and x86)
>>>>>
>>>>> Ross
>>>>>
>>>>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20160919/80f92917/attachment-0002.html>