Re: [MTT users] [MTT] #245: Support multiplicative effect for other INI params

[Ethan Mallove]

On Tue, Sep/04/2007 12:47:29PM, Jeff Squyres wrote:
> On Sep 4, 2007, at 10:57 AM, Ethan Mallove wrote:
> 
> > So if I have the following line in my [Test build: intel]
> > section, MTT will now build and run the Intel tests *twice*?
> > Once with compiler-A and once with compiler-B?
> >
> >   setenv = ("/path/to/compiler-A", "/path/to/compiler-B")
> 
> setenv is a bad example -- we can already take multiple values for  
> that and we do *not* create multiple runs for it.  For example:
> 
> setenv = FOO value1
> setenv = BAR value2
> 
> The mtt client is smart enough just to do 2 setenv's in a single  
> instance.

This ticket should be re-opened because the above case is
not covered. I *want* to get two separate test builds if I
give "prepend_path" a two-item list. Should we support two
kinds of environment INI parameter assignment? One for when
the user wants a multiplicative effect, and one for when
they do not? E.g.,

Do one test build. Prepend PATH with value1 and value2.

  prepend_path = < 
> I think that you can have some places that don't make sense to have  
> multiple values, and perhaps we should put in safeguards to ensure  
> that the INI file doesn't mistakenly do that.  For example:
> 
> module = (foo, bar)
> 
> That would be bad.  :-)
> 
> But this issue has always been around -- it's just that you can now do:
> 
> module = @foo@
> foo = (foo, bar)
> 
> 
> > -Ethan
> >
> >
> > On Tue, Sep/04/2007 10:03:09AM, Jeff Squyres wrote:
> >> I think we'll get it for everything because of the new @foo@ syntax.
> >>
> >> I don't think you'll want to use that effect everywhere, but it's now
> >> *possible* to do so.
> >>
> >>
> >> On Sep 4, 2007, at 9:57 AM, Ethan Mallove wrote:
> >>
> >>> So we will get a multiplicative effect on the following INI
> >>> parameters?
> >>>
> >>>   * setenv
> >>>   * unsetenv
> >>>   * env_module
> >>>
> >>> Any other parameters?
> >>>
> >>> -Ethan
> >>>
> >>>
> >>> On Fri, Aug/31/2007 10:18:30PM, MTT wrote:
>  #245: Support multiplicative effect for other INI params
>  --
>  +-
>    Reporter:  emallove |   Owner:
>    Type:  enhancement  |  Status:  closed
>    Priority:  major|   Milestone:  v3.0
>   Component:  Client side  | Version:  trunk
>  Resolution:  fixed|Keywords:  multiplicative exec INI
>  --
>  +-
>  Changes (by jsquyres):
> 
>    * status:  new => closed
>    * resolution:  => fixed
> 
>  Comment:
> 
>   This is now done on the jms-new-parser branch.
> 
>  -- 
>  Ticket URL:   245#comment:2>
>  MTT 
>  Issue tracking for the MPI Testing Tool.
> >>> ___
> >>> mtt-users mailing list
> >>> mtt-us...@open-mpi.org
> >>> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
> >>
> >>
> >> -- 
> >> Jeff Squyres
> >> Cisco Systems
> >>
> >> ___
> >> mtt-users mailing list
> >> mtt-us...@open-mpi.org
> >> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
> > ___
> > mtt-users mailing list
> > mtt-us...@open-mpi.org
> > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
> 
> 
> -- 
> Jeff Squyres
> Cisco Systems
> 
> ___
> mtt-users mailing list
> mtt-us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users

Re: [MTT users] [MTT] #245: Support multiplicative effect for other INI params

[Jeff Squyres]

On Sep 4, 2007, at 10:57 AM, Ethan Mallove wrote:


So if I have the following line in my [Test build: intel]
section, MTT will now build and run the Intel tests *twice*?
Once with compiler-A and once with compiler-B?

  setenv = ("/path/to/compiler-A", "/path/to/compiler-B")


setenv is a bad example -- we can already take multiple values for  
that and we do *not* create multiple runs for it.  For example:


setenv = FOO value1
setenv = BAR value2

The mtt client is smart enough just to do 2 setenv's in a single  
instance.


I think that you can have some places that don't make sense to have  
multiple values, and perhaps we should put in safeguards to ensure  
that the INI file doesn't mistakenly do that.  For example:


module = (foo, bar)

That would be bad.  :-)

But this issue has always been around -- it's just that you can now do:

module = @foo@
foo = (foo, bar)



-Ethan


On Tue, Sep/04/2007 10:03:09AM, Jeff Squyres wrote:

I think we'll get it for everything because of the new @foo@ syntax.

I don't think you'll want to use that effect everywhere, but it's now
*possible* to do so.


On Sep 4, 2007, at 9:57 AM, Ethan Mallove wrote:


So we will get a multiplicative effect on the following INI
parameters?

  * setenv
  * unsetenv
  * env_module

Any other parameters?

-Ethan


On Fri, Aug/31/2007 10:18:30PM, MTT wrote:

#245: Support multiplicative effect for other INI params
--
+-
  Reporter:  emallove |   Owner:
  Type:  enhancement  |  Status:  closed
  Priority:  major|   Milestone:  v3.0
 Component:  Client side  | Version:  trunk
Resolution:  fixed|Keywords:  multiplicative exec INI
--
+-
Changes (by jsquyres):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 This is now done on the jms-new-parser branch.

--
Ticket URL: 

MTT 
Issue tracking for the MPI Testing Tool.

___
mtt-users mailing list
mtt-us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users



--
Jeff Squyres
Cisco Systems

___
mtt-users mailing list
mtt-us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users

___
mtt-users mailing list
mtt-us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users



--
Jeff Squyres
Cisco Systems

[MTT users] Associating "description" with a single phase

[Ethan Mallove]

reporter.php has a search field for "description", but which
phase is that for? MPI Install, Test build, or Test run? A
scenario is that Sun will have a home-grown "funclet_files"
funclet set the "description" in the Install phase (e.g., a
label identifying which ISO is being tested). It would be
useful to have one of two things:

  * [easier] Have the "description" fields broken out in
reporter by phase. E.g.,
* MPI Install description
* Test build description
* Test run description
  * [harder] Be able to have a phase description carry over
to subsequent phases. I think the logic should work like
this: if an MPI Install has a description, then this
description will carry-over to its Test build and Test
runs if another description is not specified in those
post-MPI-Install phases. (Same for Test build.)

-Ethan

Re: [MTT users] [MTT] #245: Support multiplicative effect for other INI params

[Ethan Mallove]

So if I have the following line in my [Test build: intel]
section, MTT will now build and run the Intel tests *twice*?
Once with compiler-A and once with compiler-B?

  setenv = ("/path/to/compiler-A", "/path/to/compiler-B")

-Ethan


On Tue, Sep/04/2007 10:03:09AM, Jeff Squyres wrote:
> I think we'll get it for everything because of the new @foo@ syntax.
> 
> I don't think you'll want to use that effect everywhere, but it's now  
> *possible* to do so.
> 
> 
> On Sep 4, 2007, at 9:57 AM, Ethan Mallove wrote:
> 
> > So we will get a multiplicative effect on the following INI
> > parameters?
> >
> >   * setenv
> >   * unsetenv
> >   * env_module
> >
> > Any other parameters?
> >
> > -Ethan
> >
> >
> > On Fri, Aug/31/2007 10:18:30PM, MTT wrote:
> >> #245: Support multiplicative effect for other INI params
> >> -- 
> >> +-
> >>   Reporter:  emallove |   Owner:
> >>   Type:  enhancement  |  Status:  closed
> >>   Priority:  major|   Milestone:  v3.0
> >>  Component:  Client side  | Version:  trunk
> >> Resolution:  fixed|Keywords:  multiplicative exec INI
> >> -- 
> >> +-
> >> Changes (by jsquyres):
> >>
> >>   * status:  new => closed
> >>   * resolution:  => fixed
> >>
> >> Comment:
> >>
> >>  This is now done on the jms-new-parser branch.
> >>
> >> -- 
> >> Ticket URL: 
> >> MTT 
> >> Issue tracking for the MPI Testing Tool.
> > ___
> > mtt-users mailing list
> > mtt-us...@open-mpi.org
> > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
> 
> 
> -- 
> Jeff Squyres
> Cisco Systems
> 
> ___
> mtt-users mailing list
> mtt-us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users

Re: [MTT users] [MTT] #245: Support multiplicative effect for other INI params

[Ethan Mallove]

So we will get a multiplicative effect on the following INI
parameters? 

  * setenv
  * unsetenv
  * env_module

Any other parameters?

-Ethan


On Fri, Aug/31/2007 10:18:30PM, MTT wrote:
> #245: Support multiplicative effect for other INI params
> --+-
>   Reporter:  emallove |   Owner: 
>   Type:  enhancement  |  Status:  closed 
>   Priority:  major|   Milestone:  v3.0   
>  Component:  Client side  | Version:  trunk  
> Resolution:  fixed|Keywords:  multiplicative exec INI
> --+-
> Changes (by jsquyres):
> 
>   * status:  new => closed
>   * resolution:  => fixed
> 
> Comment:
> 
>  This is now done on the jms-new-parser branch.
> 
> -- 
> Ticket URL: 
> MTT 
> Issue tracking for the MPI Testing Tool.