From: Csaba Raduly <rcsaba@gmail.com>
To: Kevin Connor Arpe <kevinarpe@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: Writing unit tests for newlib/libc/unix/dirname.c
Date: Thu, 17 Nov 2022 09:11:11 +0100 [thread overview]
Message-ID: <CAEhDDbDPXBwywWvQgCibZ_AxuXDn6qy_PErBinmrrFQ9ZV6kUg@mail.gmail.com> (raw)
In-Reply-To: <CAFMYRROEHB==jFzTCw7tVwa4_9eg5eg6igmi0ZshsT4YyKs0Cw@mail.gmail.com>
On Wed, 16 Nov 2022 at 18:57, Kevin Connor Arpe wrote:
> I am trying to write unit tests for newlib/libc/unix/dirname.c.
> (That function has so many tricky corner cases!)
> I tried to follow from: newlib/testsuite/newlib.string/memcpy-1.c
> However, I cannot make unit tests run via: make test
>
> What am I doing wrong?
You didn't tell us what happened when you ran make test.
Csaba
--
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformant way
to get the wrong information: this is what you want. - Scott Meyers (C++TDaWYK)
prev parent reply other threads:[~2022-11-17 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 17:56 Kevin Connor Arpe
2022-11-17 8:11 ` Csaba Raduly [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=CAEhDDbDPXBwywWvQgCibZ_AxuXDn6qy_PErBinmrrFQ9ZV6kUg@mail.gmail.com \
--to=rcsaba@gmail.com \
--cc=cygwin@cygwin.com \
--cc=kevinarpe@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).