All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@patchwork.openembedded.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for kernel-yocto: consolidated pull request
Date: Wed, 05 Feb 2020 23:32:00 -0000	[thread overview]
Message-ID: <20200205233200.2276.7050@do> (raw)
In-Reply-To: <cover.1580944129.git.bruce.ashfield@gmail.com>

== Series Details ==

Series: kernel-yocto: consolidated pull request
Revision: 1
URL   : https://patchwork.openembedded.org/series/22442/
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            [8/9] kernel-yocto.bbclass: do_kernel_configme: don't use +errexit, merge_config_build.log and fail when /.config wasn't created
 Issue             Commit shortlog is too long [test_shortlog_length] 
  Suggested fix    Edit shortlog so that it is 90 characters or less (currently 122 characters)



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-02-05 23:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-05 23:12 [PATCH 0/9] kernel-yocto: consolidated pull request bruce.ashfield
2020-02-05 23:12 ` [PATCH 1/9] kern-tools: tweak symbol_why to be python safe bruce.ashfield
2020-02-05 23:12 ` [PATCH 2/9] kern-tools: integrate merge_config fix for gold linker bruce.ashfield
2020-02-05 23:12 ` [PATCH 3/9] kern-tools-native: use more common S value and oe_runmake bruce.ashfield
2020-02-05 23:12 ` [PATCH 4/9] kernel-yocto: Move defaults and tasks from linux-yocto.inc into bbclass bruce.ashfield
2020-02-05 23:12 ` [PATCH 5/9] kernel-yocto: Drop setting of unused variables in do_kernel_metadata bruce.ashfield
2020-02-05 23:12 ` [PATCH 6/9] kernel-yocto: Only override CONFIG_LOCALVERSION if LINUX_VERSION_EXTENSION is set bruce.ashfield
2020-02-05 23:12 ` [PATCH 7/9] kernel-yocto.bbclass: set KERNEL_LD also for merge_config.sh bruce.ashfield
2020-02-05 23:12 ` [PATCH 8/9] kernel-yocto.bbclass: do_kernel_configme: don't use +errexit, merge_config_build.log and fail when /.config wasn't created bruce.ashfield
2020-02-05 23:12 ` [PATCH 9/9] kernel-yocto: fix defconfig detection in find_sccs() bruce.ashfield
2020-02-05 23:32 ` Patchwork [this message]
2020-02-06  9:03 ` [PATCH 0/9] kernel-yocto: consolidated pull request Richard Purdie
2020-02-06 13:25   ` Bruce Ashfield
  -- strict thread matches above, loose matches on Subject: below --
2020-02-06 17:35 [PATCH 00/10][v2] " bruce.ashfield
2020-02-06 18:02 ` ✗ patchtest: failure for " Patchwork
2018-03-06 18:11 [PATCH 0/9] " Bruce Ashfield
2018-03-06 18:33 ` ✗ patchtest: failure for " Patchwork
2018-02-19  2:25 [PATCH 0/7] " Bruce Ashfield
2018-02-19  3:03 ` ✗ patchtest: failure for " Patchwork
2018-01-26 13:59 [PATCH 00/12] " Bruce Ashfield
2018-01-26 14:32 ` ✗ patchtest: failure for " Patchwork
2017-08-21  2:58 [PATCH 0/9] " Bruce Ashfield
2017-08-21  3:05 ` ✗ patchtest: failure for " 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=20200205233200.2276.7050@do \
    --to=patchwork@patchwork.openembedded.org \
    --cc=bruce.ashfield@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 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.