From: Patchwork <patchwork@patchwork.openembedded.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for glibc: Upgrade to 2.28
Date: Fri, 03 Aug 2018 17:34:17 -0000 [thread overview]
Message-ID: <20180803173417.13840.92102@do.openembedded.org> (raw)
In-Reply-To: <20180803171539.36391-1-raj.khem@gmail.com>
== Series Details ==
Series: glibc: Upgrade to 2.28
Revision: 1
URL : https://patchwork.openembedded.org/series/13377/
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 Patches not removed from tree [test_src_uri_left_files]
Suggested fix Amend the patch containing the software patch file removal
Patch 0016-Remove-bash-dependency-for-nscd-init-script.patch
Patch 0019-eglibc-Clear-cache-lines-on-ppc8xx.patch
Patch 0006-readlib-Add-OECORE_KNOWN_INTERPRETER_NAMES-to-known-.patch
Patch 0014-yes-within-the-path-sets-wrong-config-variables.patch
Patch 0015-timezone-re-written-tzselect-as-posix-sh.patch
Patch 0018-eglibc-Help-bootstrap-cross-toolchain.patch
Patch 0005-fsl-e500-e5500-e6500-603e-fsqrt-implementation.patch
Patch 0007-ppc-sqrt-Fix-undefined-reference-to-__sqrt_finite.patch
Patch 0009-Quote-from-bug-1443-which-explains-what-the-patch-do.patch
Patch 0012-sysdeps-gnu-configure.ac-handle-correctly-libc_cv_ro.patch
Patch 0008-__ieee754_sqrt-f-are-now-inline-functions-and-call-o.patch
Patch 0013-Add-unused-attribute.patch
Patch 0011-__ieee754_sqrt-f-are-now-inline-functions-and-call-o.patch
Patch 0020-eglibc-Resolve-__fpscr_values-on-SH4.patch
Patch 0010-eglibc-run-libm-err-tab.pl-with-specific-dirs-in-S.patch
Patch 0030-plural_c_no_preprocessor_lines.patch
Patch 0017-eglibc-Cross-building-and-testing-instructions.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
prev parent reply other threads:[~2018-08-03 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 17:15 [RFT][PATCH] glibc: Upgrade to 2.28 Khem Raj
2018-08-03 17: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=20180803173417.13840.92102@do.openembedded.org \
--to=patchwork@patchwork.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.