|
From: Nicholas N. <n.n...@gm...> - 2009-07-07 11:56:02
|
On Tue, Jul 7, 2009 at 8:01 PM, Ashley Pittman<as...@pi...> wrote: > > I'm looking at spending a couple of days fixing up the regtests so they > work with VPATH builds, this is probably going to end up being > moderately intrusive however. > > Is there anything I need to know before I start hacking away at the > code, are all the tests driven from "make regtest" for example or are > there other ways of driving them that I need to preserve? The arguments to vg_regtest can be entire directories or individual test files (with or without the .vgtest suffix). So all these kinds of invocations must be preserved: perl tests/vg_regtest memcheck/ perl tests/vg_regtest memcheck/addressable.vgtest perl tests/vg_regtest memcheck/addressable > One thing that springs to mind is that platform_test could be removed > and the logic rolled back into vg_regtest for example, is there any > reason why I shouldn't do this? Not that I can see; vg_regtest seems to be the only user of platform_test. Nick |