[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: using atlocal variables in autotest macros

From: Ralf Wildenhues
Subject: Re: using atlocal variables in autotest macros
Date: Tue, 3 Mar 2009 21:50:37 +0100
User-agent: Mutt/1.5.18 (2008-05-17)

* John Wohlbier wrote on Tue, Mar 03, 2009 at 09:09:09PM CET:
> That seems like a reasonable suggestion. What I have a hard time seeing
> though is how exactly I'd get that test to execute just once for serial, and
> a test writer specified number of times with different numbers of processors
> for the parallel tests. What I have now for a test is something like

> where I'd like the test author to be able to specify the numbers of
> processors they want the parallel test to run with just by writing a file
> such as this.

Why the test author, and not the user of the package?
You can specify shell variables as arguments to the testsuite
(or hard-code them in the makefile if you like) and use them in the
  ./testsuite PES="1 2 4 8 1024"

  for PE in $PES; do
    if test $PE -eq 1; then
      AT_CHECK([mpirun -n $PE ...])

> Thanks for the heads up. I've changed mpirun to mpiexec. I think I am not
> able to anticipate every system we'll run on so I'll just have to take them
> as they come and try to increase portability as we go.

Good strategy.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]