On Sep 4, 2007, at 1:33 PM, 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 = &enumerate("/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
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 = <<EOT
PATH value1
PATH value2
EOT
Do two test builds. Prepend PATH with value1 on first
build. Prepend PATH with value2 on second build.
prepend_path = <<EOT
&enumerate( \
"PATH value1", \
"PATH value2" \
)
EOT
So scalar context means do not mulitply runs, and list
context means multiply.
I might be convinced that this is ok, but you'll need to run it by
all users to make sure that they're not already using the moral
equivalent of the second form (i.e., two setenv's).
--
Jeff Squyres
Cisco Systems