From: Patchwork <patchwork@patchwork.openembedded.org>
To: Joel Stanley <joel@jms.id.au>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for GCC 7.3 fixes (rev2)
Date: Mon, 30 Jul 2018 05:32:56 -0000 [thread overview]
Message-ID: <20180730053256.13843.13813@do.openembedded.org> (raw)
In-Reply-To: <20180730051029.5530-1-joel@jms.id.au>
== Series Details ==
Series: GCC 7.3 fixes (rev2)
Revision: 2
URL : https://patchwork.openembedded.org/series/13290/
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 A patch file has been added, but does not have a Signed-off-by tag [test_signed_off_by_presence]
Suggested fix Sign off the added patch file (meta/recipes-devtools/gcc/gcc-7.3/0001-Fix-ppc64le-build-Partial-backport-r256656.patch)
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-07-30 5:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 5:10 [PATCH v2 0/2] GCC 7.3 fixes Joel Stanley
2018-07-30 5:10 ` [PATCH v2 1/2] gcc-7.3: Fix build on ppc64le hosts Joel Stanley
2018-07-30 5:10 ` [PATCH v2 2/2] gcc-7.3: Backport fixes for std::pair high memory usage Joel Stanley
2018-07-30 5:32 ` Patchwork [this message]
2018-07-30 16:38 ` [PATCH v2 0/2] GCC 7.3 fixes akuster808
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=20180730053256.13843.13813@do.openembedded.org \
--to=patchwork@patchwork.openembedded.org \
--cc=joel@jms.id.au \
--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