From: Patchwork <patchwork@patchwork.openembedded.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for gcc6: Upgrade to 6.4.0 (latest stable series release) (rev3)
Date: Sat, 10 Mar 2018 00:00:58 -0000 [thread overview]
Message-ID: <20180310000058.15536.85416@do.openembedded.org> (raw)
In-Reply-To: <1520639372-12916-1-git-send-email-juro.bystricky@intel.com>
== Series Details ==
Series: gcc6: Upgrade to 6.4.0 (latest stable series release) (rev3)
Revision: 3
URL : https://patchwork.openembedded.org/series/11226/
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 in incorrect format [test_upstream_status_presence_format]
Suggested fix Fix Upstream-Status format in 0001-enable-FL_LPAE-flag-for-armv7ve-cores.patch
Current UpStream-Status: Backport
Standard format Upstream-Status: <Valid status>
Valid status Pending, Accepted, Backport, Denied, Inappropriate [reason], Submitted [where]
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-03-10 0:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 23:49 [morty][PATCH v2] gcc6.4 upgrade Juro Bystricky
2018-03-09 23:49 ` [morty][PATCH v2] gcc6: Upgrade to 6.4.0 (latest stable series release) Juro Bystricky
2018-03-09 23:56 ` [morty][PATCH v2] gcc6.4 upgrade Bystricky, Juro
2018-03-10 0:36 ` akuster808
2018-03-10 7:46 ` Martin Jansa
2018-03-10 18:27 ` Richard Purdie
2018-03-10 21:04 ` Martin Jansa
2018-03-10 21:06 ` Martin Jansa
2018-03-10 21:34 ` Richard Purdie
2018-03-10 22:20 ` Andre McCurdy
2018-03-11 0:56 ` Martin Jansa
2018-03-11 12:06 ` Richard Purdie
2018-03-10 0:00 ` Patchwork [this message]
2018-03-10 3:30 ` ✗ patchtest: failure for gcc6: Upgrade to 6.4.0 (latest stable series release) (rev3) Andre McCurdy
2018-03-11 1:21 ` Martin Jansa
2018-03-10 1:42 ` [morty][PATCH v2] gcc6.4 upgrade Khem Raj
2018-03-10 2:25 ` Bystricky, Juro
2018-03-10 2:55 ` Andre McCurdy
2018-03-10 4:20 ` Khem Raj
2018-03-10 18:28 ` Bystricky, Juro
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=20180310000058.15536.85416@do.openembedded.org \
--to=patchwork@patchwork.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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