From: <tomas@tuxteam.de>
To: Jeffrey Walton <noloader@gmail.com>,
Peng Yu <pengyu.ut@gmail.com>,
libc-help <libc-help@sourceware.org>
Subject: Re: Does glibc has complete test coverage?
Date: Wed, 24 Mar 2021 09:32:32 +0100 [thread overview]
Message-ID: <20210324083232.GA30513@tuxteam.de> (raw)
In-Reply-To: <YFqSQ7zERwbe/aoZ@vapier>
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
On Tue, Mar 23, 2021 at 09:13:39PM -0400, Mike Frysinger via Libc-help wrote:
> On 23 Mar 2021 17:02, Jeffrey Walton wrote:
[...]
> > Test cases are monkey work that should be delegated. When delegation
> > does not occur it usually points back to shortcomings in project
> > management.
I don't know whether Jeffrey is trying to insult monkeys here...
or interns ;-P
> many are good for delegation, but that doesn't mean quantity is the same as
> quality. if we could get 100% coverage but it took weeks to run, but 90%
> coverage took <1 hour, is that 10% worth it ? this isn't exactly hyperbole
> when we have targets that run on simulators or FPGAs and have <<1GHz CPUs.
That's the point. On paper, test coverage sounds good (and tests, of
course are a worthy goal). Reality is harsh, doubly so in the case of
an OS abstraction layer like libc. Just imagine the test harness you'd
need to cover 100% of the stuff lying /below/ libc. Emulating that is
possible (up to some point), but Someone(TM) gotta do it.
So, Peng Yu, Jeffrey -- I think I read this already twice in this thread:
"patches welcome" :-)
Cheers
- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2021-03-24 8:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 16:39 Peng Yu
2021-03-23 20:41 ` Mike Frysinger
2021-03-23 21:02 ` Jeffrey Walton
2021-03-23 23:09 ` Peng Yu
2021-03-24 1:17 ` Mike Frysinger
2021-03-24 1:13 ` Mike Frysinger
2021-03-24 3:13 ` Peng Yu
2021-03-24 12:31 ` Adhemerval Zanella
2021-03-24 8:32 ` tomas [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=20210324083232.GA30513@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=libc-help@sourceware.org \
--cc=noloader@gmail.com \
--cc=pengyu.ut@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 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).