Re: CVS commit: src/tests

[Julio Merino <jmmv%NetBSD.org@localhost>]

On 6/15/11 3:36 AM, Christos Zoulas wrote:
> On Jun 14,  5:14am, jruohonen%iki.fi@localhost (Jukka Ruohonen) wrote:
> -- Subject: Re: CVS commit: src/tests
>
> | On Sat, Jun 11, 2011 at 02:03:20PM -0400, Christos Zoulas wrote:
> |>  Log Message:
> |>  Turn warns on for all tests and fix all the bugs.
> |
> | Thanks for the cleanup.
> |
> | Now the "wscrl"-test (lib/libcurses/t_curses) however fails:
> |
>
> Peeling though the layers and trying to figure out what's going on is really
> annoying. So:
>
> Let's start: t_curses is a shell script.
>
> Try to run it from source:
>
>         $ cd /usr/src/tests/lib/libcurses
>         $ atf-run obj.amd64/t_curses
>         atf-run: ERROR: Cannot open Atffile

$ cd /usr/src/tests/lib/libcurses
$ make test

> Beautiful, we have a command that takes arguments from the command line,
> the environment, and has default arguments, that I need to read the source
> to find them.
>
> I won't bore you any more with this, but I am still peeling layers of brown
> cylindrical items to find out what's going on with the test program.
>
> Surely, there must be a simpler way to isolate the test program that is
> running so that I can run it by hand and debug it! So what is it?

I'm not sure how the curses tests work, but based on what you show above 
they seem complex.  In general, just doing the "t_foo bar" dance is 
enough for debugging.

--
Julio Merino / @jmmv