From: Joe MacDonald <Joe_MacDonald@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: ✗ patchtest: failure for deprecated.bbclass: Add a PNDEPRECATED variable for recipes (rev3)
Date: Mon, 27 Feb 2017 15:06:25 -0500 [thread overview]
Message-ID: <20170227200624.GA1688@mentor.com> (raw)
In-Reply-To: <20170227183329.9748.13885@do.openembedded.org>
[-- Attachment #1: Type: text/plain, Size: 2001 bytes --]
[✗ patchtest: failure for deprecated.bbclass: Add a PNDEPRECATED variable for recipes (rev3)] On 17.02.27 (Mon 18:33) Patchwork wrote:
> == Series Details ==
>
> Series: deprecated.bbclass: Add a PNDEPRECATED variable for recipes (rev3)
> Revision: 3
> URL : https://patchwork.openembedded.org/series/5489/
> 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 65cfc8aca3)
I had been out of date, but this time I'm reasonably confident v3 is
still directly on top of master.
yocto-mainline> git config --local --get-regexp '^remote'
remote.yocto.url git://git.yoctoproject.org/poky
remote.yocto.projectname poky
remote.yocto.fetch +refs/heads/*:refs/remotes/yocto/*
yocto-mainline> git pull
Already up-to-date.
yocto-mainline> git status
On branch master
Your branch is ahead of 'yocto/master' by 1 commit.
(use "git push" to publish your local commits)
nothing to commit, working directory clean
Is patchtest having a bad day?
> 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
>
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
next prev parent reply other threads:[~2017-02-27 20:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 4:00 [PATCH] deprecated.bbclass: Add a PNDEPRECATED variable for recipes Joe MacDonald
2017-02-24 4:55 ` Khem Raj
2017-02-24 9:16 ` Martin Jansa
2017-02-24 20:39 ` Philip Balister
2017-02-24 20:51 ` Martin Jansa
2017-02-27 13:50 ` Joe MacDonald
2017-02-24 15:30 ` [PATCH v2] " Joe MacDonald
2017-02-27 13:59 ` [PATCH v3] " Joe MacDonald
[not found] ` <20170227183329.9748.13885@do.openembedded.org>
2017-02-27 20:06 ` Joe MacDonald [this message]
2017-02-27 20:25 ` ✗ patchtest: failure for deprecated.bbclass: Add a PNDEPRECATED variable for recipes (rev3) Leonardo Sandoval
2017-02-27 22:24 ` Joe MacDonald
2017-03-03 13:57 ` [PATCH v4] deprecated.bbclass: Add a PNDEPRECATED variable for recipes Joe MacDonald
2017-03-03 14:01 ` [PATCH] deprecated.bbclass: Document PNDEPRECATED variable Joe MacDonald
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=20170227200624.GA1688@mentor.com \
--to=joe_macdonald@mentor.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 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.