From: Patchwork <patchwork@patchwork.openembedded.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for YOCTO #12937 - Consistent naming scheme for deployed artifacts (rev3)
Date: Sat, 12 Oct 2019 13:32:17 -0000 [thread overview]
Message-ID: <20191012133217.2330.67122@do> (raw)
In-Reply-To: <cover.1570885333.git.Martin.Jansa@gmail.com>
== Series Details ==
Series: YOCTO #12937 - Consistent naming scheme for deployed artifacts (rev3)
Revision: 3
URL : https://patchwork.openembedded.org/series/19321/
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 [RESEND, 2/6] bitbake.conf, kernel*.bbclass: include IMAGE_VERSION_SUFFIX only in the _LINK_NAME variables and change it to hard link
Issue Commit shortlog is too long [test_shortlog_length]
Suggested fix Edit shortlog so that it is 90 characters or less (currently 119 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
next prev parent reply other threads:[~2019-10-12 13:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 13:03 [PATCH][RESEND 0/6] YOCTO #12937 - Consistent naming scheme for deployed artifacts Martin Jansa
2019-10-12 13:03 ` [PATCH][RESEND 1/6] image-artifact-names: introduce new bbclass and move some variables into it Martin Jansa
2019-10-12 13:03 ` [PATCH][RESEND 2/6] bitbake.conf, kernel*.bbclass: include IMAGE_VERSION_SUFFIX only in the _LINK_NAME variables and change it to hard link Martin Jansa
2019-10-12 13:03 ` [PATCH][RESEND 3/6] kernel-artifact-names.bbclass: use PR instead of PKGR in KERNEL_ARTIFACT_NAME Martin Jansa
2019-10-12 13:03 ` [PATCH][RESEND 4/6] kernel.bbclass: imageType without {} Martin Jansa
2019-10-12 13:03 ` [PATCH][RESEND 5/6] kernel.bbclass: drop unnecessary package_get_auto_pr for do_install Martin Jansa
2019-10-12 13:03 ` [PATCH][RESEND 6/6] *-artifact-names: include version only in the artifact links Martin Jansa
2019-10-12 13:32 ` Patchwork [this message]
2019-10-13 13:44 ` [PATCH][RESEND 0/6] YOCTO #12937 - Consistent naming scheme for deployed artifacts Richard Purdie
2019-10-17 17:50 ` Martin Jansa
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=20191012133217.2330.67122@do \
--to=patchwork@patchwork.openembedded.org \
--cc=martin.jansa@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