On Mar 20, 2008, at 12:19 PM, Ethan Mallove wrote:
I sense this "do_not_run" stuff could be useful to me, but
I'm not sure. Can you give a simple use case for
"do_not_run"? Could "do_not_run" be achieved by just
commenting out the INI lines that pertain to a certain
group? E.g., do these "#" comments ...
# simple_really_slow:tests = src/MPI_Isend_flood_c src/
MPI_Send_flood_c
No, because if an upper-level &find_executables() found
MPI_*end_flood_c, then they'll run in that section (vs. the
simple_really_slow subsection). The intent was to have a mechanism to
specify: here's some tests, exclude them from all other sections, but
*don't* run them.
# simple_really_slow:pass = &and(&test_wifexited(),
&eq(&test_wexitstatus(), 0))
# simple_really_slow:exclusive = 1
# simple_really_slow:timeout = &sum(90, &multiply(3, &test_np()))
... have the same effect as this?
simple_really_slow:do_not_run = 1
Instead, you'd have:
simple_really_slow:tests = src/MPI_Isend_flood_c src/MPI_Send_flood_c
simple_really_slow:do_not_run = 1
--
Jeff Squyres
Cisco Systems
