From: Patchwork <patchwork@patchwork.openembedded.org>
To: douglas.royds <douglas.royds@taitradio.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for glibc: Fix non-IA reproducibility for shared libraries
Date: Wed, 03 Oct 2018 04:34:26 -0000 [thread overview]
Message-ID: <20181003043426.13843.4724@do.openembedded.org> (raw)
In-Reply-To: <2f47bda4-deb2-9603-a151-8330f0d52e08@taitradio.com>
== Series Details ==
Series: glibc: Fix non-IA reproducibility for shared libraries
Revision: 1
URL : https://patchwork.openembedded.org/series/14338/
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-core/glibc/glibc/0034-reproducible-makehack-shared-libs.patch)
* Issue Added patch file is missing Upstream-Status in the header [test_upstream_status_presence_format]
Suggested fix Add Upstream-Status: <Valid status> to the header of meta/recipes-core/glibc/glibc/0034-reproducible-makehack-shared-libs.patch
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
prev parent reply other threads:[~2018-10-03 4:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 0:18 glibc binary reproducibility Douglas Royds
2018-09-27 0:54 ` Douglas Royds
2018-09-27 8:37 ` Richard Purdie
2018-10-02 16:58 ` Richard Purdie
2018-10-03 2:37 ` Douglas Royds
2018-10-03 2:43 ` Douglas Royds
2018-10-03 11:25 ` Richard Purdie
2018-10-03 13:31 ` Khem Raj
2018-10-03 20:55 ` Douglas Royds
2018-10-03 4:26 ` [PATCH] glibc: Fix non-IA reproducibility for shared libraries Douglas Royds
2018-10-03 4:34 ` Patchwork [this message]
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=20181003043426.13843.4724@do.openembedded.org \
--to=patchwork@patchwork.openembedded.org \
--cc=douglas.royds@taitradio.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