Re: [PATCH] big test separation POC

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] big test separation POC
Date: 2013-06-30 18:54:40
Message-ID: alpine.DEB.2.02.1306302047150.2808@localhost6.localdomain6
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Note about the POC patch limitations/questions:

- is deriving a schedule with a piece of shell okay?
or should perl/python/whatever scripting be better?

- the big_schedule is assumed "sequential", i.e. one test per line.
maybe it could/should be parallel?

- I'm not sure of the "parallel_schedule" and "big_schedule"
file names are the best possible choices.

- I'm really not sure about VPATH stuff.

- I do not understand why the makefile specifies $(srcdir) before
local files in some places.

- should the "bigcheck" target be accessible from the project root?
that is should "make bigcheck" from ../../.. work?

- the documentation is not updated, I guess something should be done
somewhere.

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2013-06-30 19:38:21 Re: [PATCH] big test separation POC
Previous Message Jeff Davis 2013-06-30 18:11:58 Re: fallocate / posix_fallocate for new WAL file creation (etc...)