public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Patchwork" <patchwork@patchwork.openembedded.org>
To: Anuj Mittal <anuj.mittal@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for zeus -next review (rev4)
Date: Mon, 06 Apr 2020 15:32:48 -0000	[thread overview]
Message-ID: <20200406153248.2277.39828@do> (raw)
In-Reply-To: <cover.1586185832.git.anuj.mittal@intel.com>

== Series Details ==

Series: zeus -next review (rev4)
Revision: 4
URL   : https://patchwork.openembedded.org/series/21451/
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:



* Patch            [zeus, 05/13] busybox: on upgrade save busybox if it is the last shell
 Issue             Yocto Project bugzilla tag is not correctly formatted [test_bugzilla_entry_format] 
  Suggested fix    Specify bugzilla ID in commit description with format: "[YOCTO #<bugzilla ID>]"



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:[~2020-04-09 20:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 15:11 [zeus][PATCH 00/13] zeus -next review Anuj Mittal
2020-04-06 15:11 ` [zeus][PATCH 01/13] u-boot-tools: Split out inc file Anuj Mittal
2020-04-06 15:11 ` [zeus][PATCH 02/13] waffle: no need to depend on target python3 Anuj Mittal
2020-04-06 15:11 ` [zeus][PATCH 03/13] lttng-modules: update to 2.10.14 Anuj Mittal
2020-04-06 15:11 ` [zeus][PATCH 04/13] glib-2.0: fix CVE-2020-6750 Anuj Mittal
2020-04-06 15:11 ` [zeus][PATCH 05/13] busybox: on upgrade save busybox if it is the last shell Anuj Mittal
2020-04-06 15:11 ` [zeus][PATCH 06/13] lib/oe/package_manager: make sure to not remove packages in apt install Anuj Mittal
2020-04-06 15:11 ` [zeus][PATCH 07/13] lib/oe/package_manager: fix handling of last package Anuj Mittal
2020-04-06 15:11 ` [zeus][PATCH 08/13] lib/oe/package_manager: collect provided package names when using debs Anuj Mittal
2020-04-06 15:11 ` [zeus][PATCH 09/13] lib/oe/package_manager: avoid installing provided packages via apt Anuj Mittal
2020-04-06 15:11 ` [zeus][PATCH 10/13] lib/oe/package_manager: don't try to rm /var/lib/opkg Anuj Mittal
2020-04-06 15:11 ` [zeus][PATCH 11/13] kernel-yocto.bbclass: Support config fragments with externalsrc Anuj Mittal
2020-04-06 15:11 ` [zeus][PATCH 12/13] perf: Fix externalsrc support Anuj Mittal
2020-04-06 15:11 ` [zeus][PATCH 13/13] kernelsrc.bbclass: " Anuj Mittal
2020-04-06 15:32 ` Patchwork [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=20200406153248.2277.39828@do \
    --to=patchwork@patchwork.openembedded.org \
    --cc=anuj.mittal@intel.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