<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 09/19/2016 03:55 PM, Bruce Ashfield
wrote:<br>
</div>
<blockquote
cite="mid:CADkTA4Ptre9P4MUr9D6dfxhHek8d5X3owr+q5mVWVFWWLxZKFA@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Sep 19, 2016 at 6:02 PM, Cal
Sullivan <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:california.l.sullivan@intel.com"
target="_blank">california.l.sullivan@intel.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">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.<br>
<br>
Is this acceptable?<br>
</blockquote>
<div><br>
</div>
<div>In the linux-yocto bbappends of the various layers ? I
keep track of the PV's in the</div>
<div>core recipes themselves, so they shouldn't need to be
modified.</div>
</div>
</div>
</div>
</blockquote>
You're right. Only the linux-yocto bbappends in meta-yocto-bsp need
MACHINE-specific PVs right now.<br>
The issue with 4.1 (used by lsb right now) in oe-core is that
LINUX_VERSION was bumped to 4.1.32 rather than 4.1.31 in error.<br>
<br>
---<br>
Cal<br>
<br>
<blockquote
cite="mid:CADkTA4Ptre9P4MUr9D6dfxhHek8d5X3owr+q5mVWVFWWLxZKFA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>Bruce</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks,<br>
Cal
<div class="HOEnZb">
<div class="h5"><br>
<br>
On 09/19/2016 01:49 PM, Saul Wold wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, 2016-09-19 at 15:55 -0400, Bruce Ashfield
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On 2016-09-19 03:53 PM, Cal Sullivan wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0
0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
Yep, these all have incorrect PVs.<br>
628bf62756 Merge tag 'v4.4.11' into
standard/base<br>
The problem seems fairly wide spread.<br>
<br>
Bruce, do you suggest updating PVs or updating
the SRCREVs (is<br>
there a<br>
good reason to keep using old SRCREVs?)?<br>
</blockquote>
Updating the SRCREVs is the right thing to do to
sync them up now.<br>
<br>
but ..<br>
<br>
at the same time, they should probably have their
own PVs, since<br>
next time up update 4.4.x, they'll fall out of
sync and fail again.<br>
<br>
</blockquote>
+1, I think that these need their own PV since they
also don't update<br>
as fast as the base qemu recipes do.<br>
<br>
Sau!<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
We want them to be aligned with the latest
-stable, but we also<br>
don't need failures every time I push a new SRCREV
and update the<br>
PV of the base recipe.<br>
<br>
Bruce<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0
0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<br>
---<br>
Cal<br>
<br>
<br>
On 09/19/2016 11:54 AM, Burton, Ross wrote:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<br>
On 19 September 2016 at 18:05, Cal Sullivan<br>
<<a moz-do-not-send="true"
href="mailto:california.l.sullivan@intel.com"
target="_blank">california.l.sullivan@intel.c<wbr>om</a><br>
<mailto:<a moz-do-not-send="true"
href="mailto:california.l.sullivan@intel.com"
target="_blank">california.l.sullivan@<wbr>intel.com</a>>>
wrote:<br>
<br>
It looks like the function is doing as
its supposed to, and<br>
we<br>
need to update some PVs or SRCREVs to
match PVs.<br>
<br>
E.g., on the error below, SRCREV
d6237b3b24 is indeed 4.1.31.<br>
<br>
<br>
And some more builders failed with 4.4:<br>
<br>
ERROR: linux-yocto-4.4.20+gitAUTOINC+<wbr>e66032e2d9_628bf62756-r0<br>
do_kernel_version_sanity_check<wbr>: Package
Version<br>
(4.4.20+gitAUTOINC+e66032e2d9_<wbr>628bf62756)
does not match of<br>
kernel<br>
being built (4.4.11). Please update the PV
variable to match the<br>
kernel source.<br>
ERROR: linux-yocto-4.4.20+gitAUTOINC+<wbr>e66032e2d9_628bf62756-r0<br>
do_kernel_version_sanity_check<wbr>: Function
failed:<br>
do_kernel_version_sanity_check (log file is
located at<br>
/home/pokybuild/yocto-autobuil<wbr>der/yocto-worker/nightly-<br>
arm/build/build/tmp/work/beagl<wbr>ebone-poky-linux-gnueabi/linux<wbr>-<br>
yocto/4.4.20+gitAUTOINC+e66032<wbr>e2d9_628bf62756-<br>
r0/temp/log.do_kernel_version_<wbr>sanity_check.30210)<br>
NOTE: recipe usbutils-008-r0: task do_fetch:
Started<br>
ERROR: Logfile of failure stored in:<br>
/home/pokybuild/yocto-autobuil<wbr>der/yocto-worker/nightly-<br>
arm/build/build/tmp/work/beagl<wbr>ebone-poky-linux-gnueabi/linux<wbr>-<br>
yocto/4.4.20+gitAUTOINC+e66032<wbr>e2d9_628bf62756-<br>
r0/temp/log.do_kernel_version_<wbr>sanity_check.30210<br>
ERROR: Task<br>
(/home/pokybuild/yocto-autobui<wbr>lder/yocto-worker/nightly-<br>
arm/build/meta/recipes-kernel/<wbr>linux/linux-<br>
yocto_4.4.bb:do_kernel_version<wbr>_sanity_check)<br>
failed with exit code '1'<br>
<br>
(ditto for ppc and x86)<br>
<br>
Ross<br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<br>
-- <br>
______________________________<wbr>_________________<br>
Openembedded-core mailing list<br>
<a moz-do-not-send="true"
href="mailto:Openembedded-core@lists.openembedded.org"
target="_blank">Openembedded-core@lists.openem<wbr>bedded.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openembedded.org/mailman/listinfo/openembedded-core"
rel="noreferrer" target="_blank">http://lists.openembedded.org/<wbr>mailman/listinfo/openembedded-<wbr>core</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">"Thou
shalt not follow the NULL pointer, for chaos and madness
await thee at its end"</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>