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.

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.



On 09/19/2016 11:54 AM, Burton, Ross wrote:

On 19 September 2016 at 18:05, Cal Sullivan
<mailto:california.l.sulli...@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
NOTE: recipe usbutils-008-r0: task do_fetch: Started
ERROR: Logfile of failure stored in:
failed with exit code '1'

(ditto for ppc and x86)


Openembedded-core mailing list

Reply via email to