At ORNL, I do this (when I have time to run MTT and time
to check the results). What I do is set up my script to
check to see if it is in a batch job. If so, it runs
the tests, like so:
mtt --verbose \
--print-time \
--no-mpi-phases --no-test-get --no-test-build \
--scratch ${SW_BLDDIR} \
--file ${HOME}/mtt-jaguarpf/ornl-pgi.ini
But, if not in a batch job, it builds OMPI and the tests, by:
mtt --verbose \
--print-time \
--no-test-run \
--scratch ${SW_BLDDIR} \
--file ${HOME}/mtt-jaguarpf/ornl-pgi.ini
In addition, I have the script, when it is not in a batch job submit
itself as a batch job, when it finishes building. So, basically, I
can fire off the build script and go work on other things.
-- Ken
-----Original Message-----
From: mtt-users-boun...@open-mpi.org
[mailto:mtt-users-boun...@open-mpi.org] On Behalf Of Barrett, Brian W
Sent: Thursday, April 30, 2009 5:17 PM
To: user list for the MPI Testing Tool
Subject: [MTT users] Splitting build and run phases
Hi all -
I have what's probably a stupid question, but I couldn't find the answer
on
the wiki.
I've currently been building OMPI and the tests then running the tests
all
in the same MTT run, all in a batch job. The problem is, that means
I've
got a bunch of nodes reserved while building OMPI, which I can't
actually
use.
Is there any way to split the two phases (build and run) so that I can
build
outside of the batch job, get the reservation, and run the tests?
Thanks,
Brian
--
Brian W. Barrett
Dept. 1423: Scalable System Software
Sandia National Laboratories
_______________________________________________
mtt-users mailing list
mtt-us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
