From: Joshua Lock <joshua.g.lock@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: [yocto-autobuilder][PATCH] CheckYoctoCompat.py: rename yocto-compat-layer to yocto-check-layer
Date: Thu, 21 Sep 2017 11:02:21 +0100 [thread overview]
Message-ID: <e07fe526-ced5-5d3e-005c-9549186be4e8@linux.intel.com> (raw)
In-Reply-To: <7ce6dd92-01aa-e06e-28b9-c66c621f51c0@linux.intel.com>
On 21/09/17 09:47, Joshua Lock wrote:
>
>
> On 21/09/17 02:36, Stephano Cetola wrote:
>> This script name was changed in the following commit:
>>
>> b46e05677b342df44829ffe8bcfbfc954e906030
>>
>> This patch updates the script name to match.
>>
>> [YOCTO #12110]
>>
>> Signed-off-by: Stephano Cetola <stephano.cetola@linux.intel.com>
>> ---
>>
>> lib/python2.7/site-packages/autobuilder/buildsteps/CheckYoctoCompat.py
>> | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git
>> a/lib/python2.7/site-packages/autobuilder/buildsteps/CheckYoctoCompat.py
>> b/lib/python2.7/site-packages/autobuilder/buildsteps/CheckYoctoCompat.py
>> index 134adaa51..62eddae50 100644
>> ---
>> a/lib/python2.7/site-packages/autobuilder/buildsteps/CheckYoctoCompat.py
>> +++
>> b/lib/python2.7/site-packages/autobuilder/buildsteps/CheckYoctoCompat.py
>> @@ -41,11 +41,12 @@ class CheckYoctoCompat(BitbakeShellCommand):
>> layerversioncore = int(self.getProperty("layerversion_core",
>> "0"))
>> # yocto-compat-layer-wrapper was introduced in Pyro
>> + # it was renamed to yocto-check-layer-wrapper Rocko
>> if layerversioncore >= 10:
>> command = ". ./oe-init-build-env;"
>> for layer in self.layers:
>> layerpath = os.path.join(builddir, layer)
>> - cmd = "yocto-compat-layer-wrapper {}".format(layerpath)
>> + cmd = "yocto-check-layer-wrapper {}".format(layerpath)
>
> This will result in failures on Pyro (layer version 10). We should either:
> a) bump the layer version check to only run this for Rocko (layer
> version 11)
I went ahead and merged it with this change.
Joshua
> b) use different program names for layer version 10 vs. layer version 11.
>
> I'm inclined to suggest a, the yocto-compat-layer scripts only really
> became useful in the Rocko cycle.
>
>
>> cmd = cmd + " || export CL_FAIL=1;"
>> command = command + cmd
>> command = command + 'if [ "$CL_FAIL" = "1" ]; then exit
>> 1; fi;'
>>
prev parent reply other threads:[~2017-09-21 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 1:36 [yocto-autobuilder][PATCH] CheckYoctoCompat.py: rename yocto-compat-layer to yocto-check-layer Stephano Cetola
2017-09-21 8:47 ` Joshua Lock
2017-09-21 10:02 ` Joshua Lock [this message]
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=e07fe526-ced5-5d3e-005c-9549186be4e8@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.