From: Paul Eggert <eggert@cs.ucla.edu>
To: Dennis Clarke <dclarke@blastwave.org>
Cc: Gnulib bugs <bug-gnulib@gnu.org>, 43665@debbugs.gnu.org
Subject: Re: bug#43665: GNU grep 3.5 has 2 failed tests on Solaris 10 sparc
Date: Mon, 28 Sep 2020 01:46:46 -0700 [thread overview]
Message-ID: <43d26207-4c91-8416-4ac6-783df550fcb6@cs.ucla.edu> (raw)
In-Reply-To: <8bb9bbe4-39c3-087b-bc89-7df325867266@blastwave.org>
On 9/27/20 11:43 PM, Dennis Clarke via Bug reports for GNU grep wrote:
> FAIL: test-nl_langinfo-mt
> =========================
>
> FAIL test-nl_langinfo-mt (exit status: 139)
>
> FAIL: test-stdalign
> ===================
>
> test-stdalign.c:98: assertion '(uintptr_t) &(static_char_alignas) %
> TEST_ALIGNMENT == 0' failed
> FAIL test-stdalign (exit status: 134)
These are Gnulib tests, not grep tests, so I wouldn't worry about them for Grep.
I'll cc this to bug-gnulib@gnu.org. The original bug report is here:
https://bugs.gnu.org/43665
next parent reply other threads:[~2020-09-28 8:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8bb9bbe4-39c3-087b-bc89-7df325867266@blastwave.org>
2020-09-28 8:46 ` Paul Eggert [this message]
2020-09-28 15:03 ` bug#43665: GNU grep 3.5 has 2 failed tests on Solaris 10 sparc Dennis Clarke
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43d26207-4c91-8416-4ac6-783df550fcb6@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=43665@debbugs.gnu.org \
--cc=bug-gnulib@gnu.org \
--cc=dclarke@blastwave.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).