We currently have two kinds of options in the test system. Options that
come from the "args" line in the TEST section of the example source, which
we will call $args, and options that come from the EXTRA_OPTIONS env var
when the test is executed, which we will call $extra_args.
Right now, in petsc_harness.sh:109, we feed the example executable the
arguments
$extra_args $args
This allows us to do things like declare EXTRA_OPTIONS="-fp_trap" for
linux-pkgs-dbg, and then allow it to be turned off for certain tests with
-fp_trap 0 in the argos line.
This setup, however, does not allow us to override any options given in
$args while running a test, which seems very restrictive. Should we create
a third class of options?
Thanks,
Matt
--
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
https://urldefense.us/v3/__https://www.cse.buffalo.edu/*knepley/__;fg!!G_uCfscf7eWS!es96ebvWwNhZgW9QAbhKl87uWMsmggCaWnv60yjXuLOqvK4co4KiyvhNTffA2KhyR42saIqyrZ93SeswmilV$
<https://urldefense.us/v3/__http://www.cse.buffalo.edu/*knepley/__;fg!!G_uCfscf7eWS!es96ebvWwNhZgW9QAbhKl87uWMsmggCaWnv60yjXuLOqvK4co4KiyvhNTffA2KhyR42saIqyrZ93SWsl1pKX$
>
