Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patchwork <patchwork@patchwork.openembedded.org>
To: Serhii Popovych <spopovyc@cisco.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for automake/autoconf: avoid path to perl interpreter hardcoding (rev2)
Date: Tue, 28 Mar 2017 19:02:27 -0000	[thread overview]
Message-ID: <20170328190227.6649.67586@do.openembedded.org> (raw)
In-Reply-To: <cover.1490722167.git.spopovyc@cisco.com>

== Series Details ==

Series: automake/autoconf: avoid path to perl interpreter hardcoding (rev2)
Revision: 2
URL   : https://patchwork.openembedded.org/series/6028/
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             Upstream-Status is in incorrect format [test_upstream_status_format] 
  Suggested fix    Fix Upstream-Status format in meta/recipes-devtools/autoconf/autoconf/autoconf-replace-w-option-in-shebangs-with-modern-use-warnings.patch so it is one of: Pending, Submitted, Accepted, Backport, Denied, Inappropriate



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



  parent reply	other threads:[~2017-03-28 19:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 18:26 [PATCH 0/2] automake/autoconf: avoid path to perl interpreter hardcoding Serhii Popovych
2017-03-28 18:26 ` [PATCH 1/2] autoconf: Adjust shebang lines to remove interpreter path hardcode Serhii Popovych
2017-03-28 18:40   ` [PATCH v2 2/2] " Serhii Popovych
2017-03-28 18:26 ` [PATCH 2/2] automake: " Serhii Popovych
2017-03-28 19:02 ` ✗ patchtest: failure for automake/autoconf: avoid path to perl interpreter hardcoding Patchwork
2017-03-28 19:02 ` Patchwork [this message]
2017-03-28 19:25   ` [PATCH v2 0/2] " Serhii Popovych
2017-03-28 19:25     ` [PATCH v3 1/2] autoconf: Adjust shebang lines to remove interpreter path hardcode Serhii Popovych
2017-03-30 16:44       ` Richard Purdie
2017-03-31 11:46         ` [PATCH v3 0/2] automake/autoconf: avoid path to perl interpreter hardcoding Serhii Popovych
2017-03-31 11:46           ` [PATCH v4 1/2] autoconf: Adjust shebang lines to remove interpreter path hardcode Serhii Popovych
2017-03-31 11:46           ` [PATCH v3 2/2] automake: " Serhii Popovych
2017-03-28 19:25     ` [PATCH v2 " Serhii Popovych
2017-03-30 16:45       ` Richard Purdie
2017-03-31 12:02     ` ✗ patchtest: failure for "[v3,1/2] autoconf: Adjust sheb..." and 1 more (rev2) Patchwork

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=20170328190227.6649.67586@do.openembedded.org \
    --to=patchwork@patchwork.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=spopovyc@cisco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox