From: Richard Purdie <rpurdie@rpsys.net>
To: Ed Bartosh <ed.bartosh@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] oe-selftest: test wic sparse_copy API
Date: Thu, 06 Apr 2017 12:13:06 +0100 [thread overview]
Message-ID: <1491477186.17200.31.camel@rpsys.net> (raw)
In-Reply-To: <1491304245-7194-1-git-send-email-ed.bartosh@linux.intel.com>
On Tue, 2017-04-04 at 14:10 +0300, Ed Bartosh wrote:
> Added new parameter 'api' to sparse_copy function to specify
> underlying filemap API to use. By default sparse_copy will
> try both available APIs.
>
> Added test case for sparse_copy to wic test suite.
>
> Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
> ---
> meta/lib/oeqa/selftest/wic.py | 26 ++++++++++++++++++++++++++
> scripts/lib/wic/filemap.py | 6 ++++--
> 2 files changed, 30 insertions(+), 2 deletions(-)
This failed on the autobuilder:
https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/244/steps/Running%20oe-selftest/logs/stdio
Cheers,
Richard
next prev parent reply other threads:[~2017-04-06 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 11:10 [PATCH] oe-selftest: test wic sparse_copy API Ed Bartosh
2017-04-04 12:02 ` ✗ patchtest: failure for " Patchwork
2017-04-06 11:13 ` Richard Purdie [this message]
2017-04-06 11:58 ` [PATCH v2] " Ed Bartosh
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=1491477186.17200.31.camel@rpsys.net \
--to=rpurdie@rpsys.net \
--cc=ed.bartosh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox