From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: improving test framework
Date: Thu, 4 Jan 2024 18:46:13 -0500 [thread overview]
Message-ID: <ZZdDRfYJlpbwcTh6@vapier> (raw)
[-- Attachment #1: Type: text/plain, Size: 439 bytes --]
the recent discussions of regressions, and with people proposing patches that
seemed buggy, makes me think the test framework is not easy to run, or that
comprehensive. seems like we should be able to configure newlib for native
builds (i.e. non-cross-compiling), and `make check` should "just work", and
we should require people add/improve tests when changing core functions.
anyone have experience with the existing framework ?
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2024-01-04 23:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ZZdDRfYJlpbwcTh6@vapier \
--to=vapier@gentoo.org \
--cc=newlib@sourceware.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).