From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: jan.kratochvil@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix `testrun.log' output of manual `testrun's
Date: Sat, 13 Jan 2007 13:47:00 -0000 [thread overview]
Message-ID: <200701131346.l0DDkrmM015237@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20070113090837.GA25646@host0.dyn.jankratochvil.net> (message from Jan Kratochvil on Sat, 13 Jan 2007 10:08:37 +0100)
> Date: Sat, 13 Jan 2007 10:08:37 +0100
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
>
> Hi,
>
> if you run by hand:
> cd gdb/testsuite; runtest gdb.base/complex.exp
> (any test using get_compiler_info())
>
> "testrun.log" will get empty (except its header).
>
> This problem does not occur during `make check'.
I always do
$ make RUNTESTFLAGS=gdb.base/complex.exp check
That works in both the gdb directory and the gdb/testsuite directory
and puts the output in gdb.log and gdb.sum.
Cheers,
Mark
next prev parent reply other threads:[~2007-01-13 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 9:08 Jan Kratochvil
2007-01-13 13:47 ` Mark Kettenis [this message]
2007-01-13 16:01 ` Daniel Jacobowitz
2007-01-14 15:34 ` Jan Kratochvil
2007-01-20 19:59 ` Daniel Jacobowitz
2007-01-21 22:28 ` Jan Kratochvil
2007-01-21 22:51 ` Daniel Jacobowitz
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=200701131346.l0DDkrmM015237@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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