From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Oleksandr Kravchuk <oleksandr.kravchuk@pelagicore.com>
Subject: Re: ✗ patchtest: failure for curl: upgradeto 7.54.0
Date: Mon, 14 Aug 2017 10:30:14 -0500 [thread overview]
Message-ID: <1502724614.28941.8.camel@linux.intel.com> (raw)
In-Reply-To: <20170811223123.2381.83800@do.openembedded.org>
On Fri, 2017-08-11 at 22:31 +0000, Patchwork wrote:
> == Series Details ==
>
> Series: curl: upgradeto 7.54.0
> Revision: 1
> URL : https://patchwork.openembedded.org/series/8196/
> 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 df7f5221a5)
current curl version is 7.54.1 so what you are trying to do is not an
upgrade.
>
> * Patch [meta-oe] curl: upgradeto 7.54.0
> Issue Series sent to the wrong mailing list [test_target_mailing_list]
> Suggested fix Check the project's README (meta-oe) and send the patch to the indicated list
>
This message is a bit misleading so let me explain what went wrong:
patchest looks in the commit shortlog for meta-* strings and if matched
it suggests to look into the proper README. But in this case, there is
no need to include the meta-oe tag because patch is targeted to oe-core.
>
>
> 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
>
prev parent reply other threads:[~2017-08-14 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 22:18 [meta-oe][PATCH] curl: upgradeto 7.54.0 Oleksandr Kravchuk
2017-08-11 22:31 ` ✗ patchtest: failure for " Patchwork
2017-08-14 15:30 ` Leonardo Sandoval [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=1502724614.28941.8.camel@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=oleksandr.kravchuk@pelagicore.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