From: Patrick Ohly <patrick.ohly@intel.com>
To: openembedded-core@lists.openembedded.org
Cc: paul.eggleton@linux.intel.com
Subject: Re: [PATCH 5/5] yocto-compat-layer: test signature differences when setting MACHINE
Date: Sat, 08 Apr 2017 12:14:35 +0200 [thread overview]
Message-ID: <1491646475.10884.82.camel@intel.com> (raw)
In-Reply-To: <ad9558050d220e86e62faabc3439132d272b5ac1.1491583077.git-series.patrick.ohly@intel.com>
On Fri, 2017-04-07 at 18:38 +0200, Patrick Ohly wrote:
> + parser.add_argument('--additional-layers', nargs="+",
> + help='List of additional layers to add during testing',
> action='store')
> parser.add_argument('-n', '--no-auto', help='Disable auto layer
> discovery',
> action='store_true')
> parser.add_argument('-d', '--debug', help='Enable debug output',
> @@ -82,6 +86,7 @@ def main():
> if not layers:
> logger.error("Fail to detect layers")
> return 1
> + additional_layers = detect_layers(args.additional_layers,
> args.no_auto)
> if args.dependency:
> dep_layers = detect_layers(args.dependency, args.no_auto)
> dep_layers = dep_layers + layers
> @@ -128,7 +133,15 @@ def main():
>
> shutil.copyfile(bblayersconf + '.backup', bblayersconf)
>
> - if not add_layer_dependencies(bblayersconf, layer,
> dep_layers, logger):
> + missing_dependencies = not
> add_layer_dependencies(bblayersconf, layer, dep_layers, logger)
> + if not missing_dependencies:
> + for additional_layer in additional_layers:
> + if not add_layer_dependencies(bblayersconf,
> additional_layer, dep_layers, logger):
> + missing_dependencies = True
> + break
> + if not add_layer_dependencies(bblayersconf, layer,
> dep_layers, logger) or \
> + any(map(lambda additional_layer: not
> add_layer_dependencies(bblayersconf, additional_layer, dep_layers,
> logger),
> + additional_layers)):
> logger.info('Skipping %s due to missing dependencies.' %
> layer['name'])
> results[layer['name']] = None
> results_status[layer['name']] = 'SKIPPED (Missing
> dependencies)'
> @@ -140,8 +153,11 @@ def main():
> logger.info('Getting initial signatures ...')
> td['builddir'] = builddir
> td['sigs'], td['tunetasks'] = get_signatures(td['builddir'])
> + td['machines'] = args.machines
>
> - if not add_layer(bblayersconf, layer, dep_layers, logger):
> + if not add_layer(bblayersconf, layer, dep_layers, logger) or
> \
> + any(map(lambda additional_layer: not
> add_layer(bblayersconf, additional_layer, dep_layers, logger),
> + additional_layers)):
Note to myself: this --additional-layers argument should be in its own
commit, and the additional layers need to be added before obtaining the
initial signatures. Otherwise the test_signatures does not test the
changes introduced by the layer under testing, but also all these
additional layers.
That's not the intention - the additional layers basically represents
what's already in a distro before adding the new layer.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
prev parent reply other threads:[~2017-04-08 10:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 16:38 [PATCH 0/5] [RFC] yocto-compat-layer: various enhancements + bitbake-diffsigs support Patrick Ohly
2017-04-07 16:38 ` [PATCH 1/5] yocto-compat-layer: fix also other command invocations Patrick Ohly
2017-04-07 16:38 ` [PATCH 2/5] yocto-compat-layer: limit report of signature changes Patrick Ohly
2017-04-07 16:38 ` [PATCH 3/5] yocto-compat-layer: include bitbake-diffsigs output Patrick Ohly
2017-04-07 16:38 ` [PATCH 4/5] yocto-compat-layer: also determine tune flags for each task Patrick Ohly
2017-04-07 16:38 ` [PATCH 5/5] yocto-compat-layer: test signature differences when setting MACHINE Patrick Ohly
2017-04-08 10:14 ` Patrick Ohly [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=1491646475.10884.82.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.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