Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patchwork <patchwork@patchwork.openembedded.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for "gobject-introspection: update ..." and 15 more
Date: Thu, 22 Nov 2018 16:07:32 -0000	[thread overview]
Message-ID: <20181122160732.2329.45072@do> (raw)
In-Reply-To: <20181122154136.121480-1-alex.kanavin@gmail.com>

== Series Details ==

Series: "gobject-introspection: update ..." and 15 more
Revision: 1
URL   : https://patchwork.openembedded.org/series/15041/
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 Inappropriate, but no reason was provided [test_upstream_status_presence_format] 
  Suggested fix    Include a brief reason why 0001-Committing-changes-from-do_unpack_extra.patch is inappropriate
  Current          Upstream-Status: Inappropriate
  Standard format  Upstream-Status: Inappropriate [reason]



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] -> ...).

---
Guidelines:     https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
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:[~2018-11-22 16:07 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-22 15:41 [PATCH 01/16] gobject-introspection: update to 1.58.1 Alexander Kanavin
2018-11-22 15:41 ` [PATCH 02/16] openssl10: update to 1.0.2q Alexander Kanavin
2018-11-22 15:41 ` [PATCH 03/16] openssl: update to 1.1.1a Alexander Kanavin
2018-11-23 23:36   ` Richard Purdie
2018-11-22 15:41 ` [PATCH 04/16] dmidecode: update to 3.2 Alexander Kanavin
2018-11-22 15:41 ` [PATCH 05/16] tiff: update to 4.0.10 Alexander Kanavin
2018-11-22 15:41 ` [PATCH 06/16] gdbm: update to 1.18.1 Alexander Kanavin
2018-11-22 15:41 ` [PATCH 07/16] icu: update to 63.1 Alexander Kanavin
2018-11-22 15:41 ` [PATCH 08/16] btrfs-tools: update to 4.19 Alexander Kanavin
2018-11-22 23:40   ` Richard Purdie
2018-11-22 15:41 ` [PATCH 09/16] vala: update to 0.42.3 Alexander Kanavin
2018-11-22 15:41 ` [PATCH 10/16] webkitgtk: update to 2.22.4 Alexander Kanavin
2018-11-22 15:41 ` [PATCH 11/16] psmisc: update to 23.2 Alexander Kanavin
2018-11-23 23:35   ` Richard Purdie
2018-11-22 15:41 ` [PATCH 12/16] sysprof: update to 3.30.2 Alexander Kanavin
2018-11-22 15:41 ` [PATCH 13/16] libwebp: update to 1.0.1 Alexander Kanavin
2018-11-22 15:41 ` [PATCH 14/16] lighttpd: update to 1.4.51 Alexander Kanavin
2018-11-22 15:41 ` [PATCH 15/16] libdnf: update to 0.22.3 Alexander Kanavin
2018-11-22 15:41 ` [PATCH 16/16] dnf: update to 4.0.9 Alexander Kanavin
2018-11-22 23:38   ` Richard Purdie
2018-11-23 15:33     ` Richard Purdie
2018-11-22 16:07 ` Patchwork [this message]
2018-11-26 22:29 ` [PATCH 01/16] gobject-introspection: update to 1.58.1 Khem Raj
2018-11-27  8:48   ` Alexander Kanavin
2018-11-27 17:58     ` Khem Raj
2018-11-27 18:59       ` Khem Raj
2018-12-02 11:23         ` Alexander Kanavin
2018-12-02 18:58           ` Khem Raj
2018-12-01 22:28       ` Alexander Kanavin
2018-12-02 18:50         ` Khem Raj
2018-12-02 22:22           ` Richard Purdie
2018-12-03 11:49             ` Alexander Kanavin

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=20181122160732.2329.45072@do \
    --to=patchwork@patchwork.openembedded.org \
    --cc=alex.kanavin@gmail.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