From: Patchwork <patchwork@patchwork.openembedded.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for Packages upgrade
Date: Mon, 05 Feb 2018 03:03:03 -0000 [thread overview]
Message-ID: <20180205030303.15542.28722@do.openembedded.org> (raw)
In-Reply-To: <cover.1517798422.git.liezhi.yang@windriver.com>
== Series Details ==
Series: Packages upgrade
Revision: 1
URL : https://patchwork.openembedded.org/series/10841/
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 LIC_FILES_CHKSUM changed on target ccache but there is no "License-Update" tag in commit message [test_lic_files_chksum_modified_not_mentioned]
Suggested fix Include "License-Update: <description>" into the commit message with a brief description
Current checksum file://LICENSE.txt;md5=7fe21f9470f2305e95e7d8a632255079
New checksum file://LICENSE.txt;md5=dae379a85bb6e9d594773e0aa64876f6
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:[~2018-02-05 3:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 2:41 [PATCH 0/4] Packages upgrade Robert Yang
2018-02-05 2:41 ` [PATCH 1/4] ccache: 3.3.4 -> 3.3.5 Robert Yang
2018-02-05 2:41 ` [PATCH 2/4] nfs-utils: 2.1.1 -> 2.3.1 Robert Yang
2018-02-15 17:13 ` Richard Purdie
2018-02-05 2:41 ` [PATCH 3/4] git: 2.15.0 -> 2.16.1 Robert Yang
2018-02-05 11:29 ` Peter Kjellerstedt
2018-02-06 4:46 ` Robert Yang
2018-02-05 2:41 ` [PATCH 4/4] time: 1.7 -> 1.8 Robert Yang
2018-02-15 18:30 ` Richard Purdie
2018-02-15 18:56 ` Andre McCurdy
2018-02-21 20:05 ` Burton, Ross
2018-02-22 2:31 ` Robert Yang
2018-02-22 2:31 ` Robert Yang
2018-02-05 3:03 ` Patchwork [this message]
2018-02-05 4:25 ` ✗ patchtest: failure for Packages upgrade Robert Yang
-- strict thread matches above, loose matches on Subject: below --
2017-02-10 3:23 [PATCH 00/10] " Robert Yang
2017-02-10 3:29 ` ✗ patchtest: failure for " Patchwork
2017-02-10 3:37 ` Robert Yang
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=20180205030303.15542.28722@do.openembedded.org \
--to=patchwork@patchwork.openembedded.org \
--cc=liezhi.yang@windriver.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