From: Denys Dmytriyenko <denis@denix.org>
To: Lev Iserovich <Lev.Iserovich@deshawresearch.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: ✗ patchtest: failure for gettext: Enable generation of libasprintf in gettext 0.19
Date: Tue, 11 Jul 2017 11:35:21 -0400 [thread overview]
Message-ID: <20170711153521.GG26405@denix.org> (raw)
In-Reply-To: <2753237e-e5ce-54e8-5a45-2dea9fed8899@deshawresearch.com>
Your patch is simply corrupted - please use git to send it, not a regular MUA.
On Tue, Jul 11, 2017 at 11:10:11AM -0400, Lev Iserovich wrote:
> Can anyone help me with undestanding this - I'm confused by this
> patchwork failure.
> The patch applies just fine on top of master - my patch was based on
> top of the commit with the hash referenced by patchwork below.
>
> Thanks,
>
> Lev Iserovich
>
> On 07/10/2017 05:31 PM, Patchwork wrote:
> >== Series Details ==
> >
> >Series: gettext: Enable generation of libasprintf in gettext 0.19
> >Revision: 1
> >URL : https://patchwork.openembedded.org/series/7657/
> >State : failure
> >
> >== Summary ==
> >
> >
> >Thank you for submitting this patch series to OpenEmbedded Core. This is
> >an automated response. Several tests have been executed on the proposed
> >series by patchtest resulting in the following failures:
> >
> >
> >
> >* Issue Series does not apply on top of target branch [test_series_merge_on_head]
> > Suggested fix Rebase your series on top of targeted branch
> > Targeted branch master (currently at 7dd5dfc4d5)
> >
> >
> >
> >If you believe any of these test results are incorrect, please reply to the
> >mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
> >Otherwise we would appreciate you correcting the issues and submitting a new
> >version of the patchset if applicable. Please ensure you add/increment the
> >version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
> >[PATCH v3] -> ...).
> >
> >---
> >Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
> >Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe
> >
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2017-07-11 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 20:37 [PATCH] gettext: Enable generation of libasprintf in gettext 0.19 Lev Iserovich
2017-07-10 21:31 ` ✗ patchtest: failure for " Patchwork
2017-07-11 15:10 ` Lev Iserovich
2017-07-11 15:35 ` Denys Dmytriyenko [this message]
2017-07-11 16:15 ` Leonardo Sandoval
2017-07-11 16:35 ` Lev Iserovich
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=20170711153521.GG26405@denix.org \
--to=denis@denix.org \
--cc=Lev.Iserovich@deshawresearch.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