From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: anelliot <amber.n.elliot@intel.com>,
openembedded-core@lists.openembedded.org
Cc: paul.eggleton@linux.intel.com
Subject: Re: [PATCH 1/1] wic: argparse now used for help functionality.
Date: Mon, 22 Jan 2018 10:16:48 +0000 [thread overview]
Message-ID: <1516616208.24502.100.camel@linuxfoundation.org> (raw)
In-Reply-To: <cfe77fab44ccf8ac32f4df117b729d65376e9da2.1516289668.git.amber.n.elliot@intel.com>
On Thu, 2018-01-18 at 07:42 -0800, anelliot wrote:
> The wic help output formally consisted of manually created strings
> mixed with argparse,
> which wasunformatted and unusable. This fix cleans up the help
> messages, rewrites help
> functionality to use argparse, and adds functionality to show
> information for
> plugins (similar to canned images).
>
> Fixes [YOCTO #12205]
>
> Signed-off-by: anelliot <amber.n.elliot@intel.com>
> ---
> meta/lib/oeqa/selftest/cases/wic.py | 58 +-
> scripts/lib/wic/engine.py | 87 ++-
> scripts/lib/wic/help.py | 1080 ++++---------------------
> ----------
> scripts/wic | 168 ++----
> 4 files changed, 269 insertions(+), 1124 deletions(-)
Unfortunately this is causing a selftest regression:
https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/771
You should be able to reproduce with:
"oe-selftest -r wic.Wic.test_qemu"
Cheers,
Richard
next prev parent reply other threads:[~2018-01-22 10:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 15:42 [PATCH 0/1] wic: argparse now used for help functionality anelliot
2018-01-18 15:42 ` [PATCH 1/1] " anelliot
2018-01-22 10:16 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-12 11:53 [PATCH 0/1] " anelliot
2017-12-12 11:54 ` [PATCH 1/1] " anelliot
2017-12-19 10:35 ` Ed Bartosh
2017-12-11 21:25 Elliot, Amber N
2017-12-12 11:52 ` Burton, Ross
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=1516616208.24502.100.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=amber.n.elliot@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