Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Cal Sullivan <california.l.sullivan@intel.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
	Saul Wold <saul.wold@intel.com>
Subject: Re: [PATCH V2 1/1] kernel.bbclass: Add kernel_version_sanity_check function
Date: Mon, 19 Sep 2016 16:02:30 -0700	[thread overview]
Message-ID: <9b22685c-2fae-0b02-899d-eced3e69a931@intel.com> (raw)
In-Reply-To: <CADkTA4Ptre9P4MUr9D6dfxhHek8d5X3owr+q5mVWVFWWLxZKFA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 5394 bytes --]



On 09/19/2016 03:55 PM, Bruce Ashfield wrote:
>
>
> On Mon, Sep 19, 2016 at 6:02 PM, Cal Sullivan 
> <california.l.sullivan@intel.com 
> <mailto:california.l.sullivan@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.
You're right. Only the linux-yocto bbappends in meta-yocto-bsp need 
MACHINE-specific PVs right now.
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.

---
Cal

>
> 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@intel.com
>                     <mailto:california.l.sullivan@intel.com>
>                     <mailto:california.l.sullivan@intel.com
>                     <mailto:california.l.sullivan@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@lists.openembedded.org
>     <mailto:Openembedded-core@lists.openembedded.org>
>     http://lists.openembedded.org/mailman/listinfo/openembedded-core
>     <http://lists.openembedded.org/mailman/listinfo/openembedded-core>
>
>
>
>
> -- 
> "Thou shalt not follow the NULL pointer, for chaos and madness await 
> thee at its end"


[-- Attachment #2: Type: text/html, Size: 10440 bytes --]

  reply	other threads:[~2016-09-19 23:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-16 23:48 [PATCH V2 1/1] kernel.bbclass: Add kernel_version_sanity_check function California Sullivan
2016-09-19 15:04 ` Bruce Ashfield
2016-09-19 15:09   ` Burton, Ross
2016-09-19 16:22     ` Burton, Ross
2016-09-19 17:05       ` Cal Sullivan
2016-09-19 18:54         ` Burton, Ross
2016-09-19 19:53           ` Cal Sullivan
2016-09-19 19:55             ` Bruce Ashfield
2016-09-19 20:49               ` Saul Wold
2016-09-19 22:02                 ` Cal Sullivan
2016-09-19 22:55                   ` Bruce Ashfield
2016-09-19 23:02                     ` Cal Sullivan [this message]
2016-09-20  0:03                       ` Bruce Ashfield
2016-09-20  3:54                         ` Bruce Ashfield
2016-09-21  3:11 ` Robert Yang
2016-09-21 16:27   ` Cal Sullivan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9b22685c-2fae-0b02-899d-eced3e69a931@intel.com \
    --to=california.l.sullivan@intel.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=saul.wold@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox