From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Tim Orling <timothy.t.orling@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/7] libtest-needs-perl: add 0.002005
Date: Sun, 04 Mar 2018 17:24:44 +0000 [thread overview]
Message-ID: <1520184284.3436.73.camel@linuxfoundation.org> (raw)
In-Reply-To: <33ac1c7b856b09d1f12d7bbf13dd9343cf27a867.1520166347.git.timothy.t.orling@linux.intel.com>
On Sun, 2018-03-04 at 04:41 -0800, Tim Orling wrote:
> Skip tests when modules not available
>
> * Dependency for ptest of liburi-perl
>
> Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com>
> ---
> .../perl/libtest-needs-perl_0.002005.bb | 29
> ++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
> create mode 100644 meta/recipes-devtools/perl/libtest-needs-
> perl_0.002005.bb
Can you send a patch to fix:
https://autobuilder.yocto.io/builders/nightly-oe-
selftest/builds/878/steps/Running%20oe-selftest/logs/stdio
i.e.
oe-selftest -r distrodata.Distrodata.test_maintainers
please? (missing maintainers entry for libtest-needs-perl)
Cheers,
Richard
next prev parent reply other threads:[~2018-03-04 17:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 12:41 [PATCH 0/7] Enable easier ptest of perl modules Tim Orling
2018-03-04 12:41 ` [PATCH 1/7] meta/classes: add ptest-perl.bbclass Tim Orling
2018-03-04 12:41 ` [PATCH 2/7] libtest-needs-perl: add 0.002005 Tim Orling
2018-03-04 17:24 ` Richard Purdie [this message]
2018-03-04 22:55 ` Tim Orling
2018-03-04 12:41 ` [PATCH 3/7] liberror-perl: inherit ptest-perl Tim Orling
2018-03-04 12:41 ` [PATCH 4/7] liburi-perl: " Tim Orling
2018-03-04 12:41 ` [PATCH 5/7] libxml-parser-perl: " Tim Orling
2018-03-04 12:41 ` [PATCH 6/7] libxml-perl: " Tim Orling
2018-03-04 12:41 ` [PATCH 7/7] libxml-simple-perl: " Tim Orling
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=1520184284.3436.73.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=timothy.t.orling@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 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.