public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: Re: [RFC] Run tests in sub dir of testsuite/
Date: Sun, 11 Jan 2015 12:36:00 -0000	[thread overview]
Message-ID: <87y4p9sdci.fsf@codesourcery.com> (raw)
In-Reply-To: <87h9wkwio8.fsf@codesourcery.com> (Yao Qi's message of "Thu, 25	Dec 2014 10:46:15 +0800")

Yao Qi <yao@codesourcery.com> writes:

> Subject: [PATCH] Run tests in sub dir of testsuite/
>
> Here is the V2, in which we have two changes,
>
>  1. Don't change the location of gdb.sum and gdb.log,
>  2. Rename sequential-tests by sequential-run.
>
> ----------------------------------------------------------------
>
> This patch is to run testsuite in a subdirectory of testsuite/, in
> order to facilitate 'make clean'.  In sequential testing, directory
> testsuite/sequential-run is created, and in parallel testing,
> directory testsuite/parallel-run is created.  Testing artifacts
> (such as directory gdb.base, gdb.ada, object files, shared libraries
> and executables) are stored in it.
>
> In testsuite/Makefile.in, we set OUTPUTDIR to either sequential-run
> or parallel-run, determined by whether we run tests in parallel.
> Makefile passes OUTPUTDIR to dejagnu, and lib/gdb.exp return the
> expected file path according to OUTPUTDIR.
>
> This patch doesn't changes the location of gdb.sum.
>
> gdb/testsuite:
>
> 2014-12-25  Yao Qi  <yao@codesourcery.com>
>
> 	* Makefile.in: Set OUTPUTDIR.
> 	(check-single): Create dir OUTPUTDIR and pass $(OUTPUTDIR) to
> 	runtest.
> 	(check-parallel): Use $(OUTPUTDIR).
> 	(check/%.exp): Pass $(OUTPUTDIR) to runtest.
> 	(check-perf): Likewise.
> 	(clean): Remove directory sequential-run and parallel-run.
> 	* lib/gdb.exp (standard_output_file): Return file path name
> 	according to new directory structure.
> 	(gdb_init): Use $OUTPUTDIR instead of outputs.
> 	(top-level): Create directory $OUTPUTDIR.
> 	* lib/trace-support.exp (get_in_proc_agent): Don't use $objdir
> 	in the path of inprocagent.
> 	* gdb.base/completion.exp: Use ${OUTPUTDIR}.
> 	* gdb.base/hashline1.exp: Use [pwd] instead of $objdir.

Could anyone take a look?

-- 
Yao (齐尧)

      reply	other threads:[~2015-01-11 12:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11  2:54 Yao Qi
2014-12-11  3:06 ` Doug Evans
2014-12-11  3:18   ` Yao Qi
2014-12-12 11:35     ` Pedro Alves
2014-12-14  6:12       ` Yao Qi
2014-12-25  2:46 ` Yao Qi
2015-01-11 12:36   ` Yao Qi [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=87y4p9sdci.fsf@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@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).