My entire Cisco setup is completely automated; I have a schedule of
what I run every night, etc. It's kinda complex and somewhat kludgey,
but it works. :-\
Have a look in the ompi-tests SVN repository:
trunk/cisco/mtt/
I run the "nightly.pl" script via cron on a cluster that is ma
Nice. Thanks.
On Tue, 2008-05-13 at 16:20 -0400, Jeff Squyres wrote:
> FWIW, I heavily use the --section and --[no]- command line
> arguments in my automated Cisco MTT setup.
>
>
> On May 13, 2008, at 4:12 PM, Ethan Mallove wrote:
>
> > On Tue, May/13/2008 02:54:46PM, Rafael Folco wrote:
>
FWIW, I heavily use the --section and --[no]- command line
arguments in my automated Cisco MTT setup.
On May 13, 2008, at 4:12 PM, Ethan Mallove wrote:
On Tue, May/13/2008 02:54:46PM, Rafael Folco wrote:
Hi,
I appreciate if anyone can give me some help.
How to run MTT tests just against o
On Tue, May/13/2008 02:54:46PM, Rafael Folco wrote:
> Hi,
>
> I appreciate if anyone can give me some help.
>
> How to run MTT tests just against one specific MPI version ? It is
> running against all MPI versions: ompi-nightly-v1.1, ompi-nightly-trunk,
> and ompi-nightly-v1.2.
>
> I've already
Hi,
I appreciate if anyone can give me some help.
How to run MTT tests just against one specific MPI version ? It is
running against all MPI versions: ompi-nightly-v1.1, ompi-nightly-trunk,
and ompi-nightly-v1.2.
I've already tried to use the following configurations. Did I miss
anything ?
MPI
On Tue, May/13/2008 11:29:33AM, Rafael Folco wrote:
> Guys,
>
> it works for me. Just comment one of those identical lines:
> #specify_module = Simple
>
>
> That's All Folco's
> :-D
>
>
>
>
> On Tue, 2008-05-13 at 10:14 -0400, Jeff Squyres wrote:
> > Ethan -- are you referring to the sample
Guys,
it works for me. Just comment one of those identical lines:
#specify_module = Simple
That's All Folco's
:-D
On Tue, 2008-05-13 at 10:14 -0400, Jeff Squyres wrote:
> Ethan -- are you referring to the sample INI file on the core-testers
> branch?
>
>
> On May 13, 2008, at 9:59 AM, Et
Ethan -- are you referring to the sample INI file on the core-testers
branch?
On May 13, 2008, at 9:59 AM, Ethan Mallove wrote:
Are you running on the ompi-core-testers branch? I think I
see a typo in the INI file. "specify_module" is defined
twice. Could you try deleting one of the "specify
Sorry for the delay on this. I probably will not have a chance to look
at it until later this week or early next. Thank you for the work on
the patch.
Cheers,
Josh
On May 12, 2008, at 8:08 AM, Pavel Shamis (Pasha) wrote:
Hi Josh,
I ported the error handling mechanism from submit/index.php
Are you running on the ompi-core-testers branch? I think I
see a typo in the INI file. "specify_module" is defined
twice. Could you try deleting one of the "specify_module"
lines, and commit the change if it solves your problem?
specify_module = Simple
simple_pass:tests = &cat("run_list")
sp
On May 13, 2008, at 2:58 AM, Wen Hao Wang wrote:
I run client/mtt with debug model, and found mtt script exited in
following code section of lib/MTT/Module.pm.
32 my $str = "require $module";
33 Debug("Evaluating: $str\n");
34 my $check = eval $str;
When require error occured, $str was set t
Hi Ethan, Thanks for your answer!
I run client/mtt with debug model, and found mtt script exited in following
code section of lib/MTT/Module.pm.
32 my $str = "require $module";
33 Debug("Evaluating: $str\n");
34 my $check = eval $str;
When require error occured, $str was set to "M
12 matches
Mail list logo
