-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
create_test does not take suite name(s) as position argument #2094
Comments
That is an interesting interpretation of the help text. Test suite names can only be used with the |
Where does it say "Test suite names can only be used with the --xml-category option."? Are you saying the phrase "or test suites" under positional arguments is incorrect? Is there a way to (for instance) run two suites for a single machine_compiler combination with a single create_test call? |
I don't think so. |
I have also been confused by this help text. So it sounds like the answer to this
is "yes"? |
@gold2718 , positional testargs are for ACME. |
@jgfouca, Of course, in this case, we could just adopt the ACME interface to create_test and solve a lot of problems (IMHO). |
Fix the description help-dump for create_test. |
Adds coupled 1950-control-run compsets at low and high resolution This PR brings in three new compsets: * A_WCYCL1950S_HR; * A_WCYCL1950S_LR; and * A_WCYCL1950S_LRtunedHR. In conjunction with this PR, new inputdata files have already been added to the svn server. We have tested that these new compsets run using short (day-long) simulations on cori-knl. It should be BFB for all other compsets [BFB]
Adds coupled 1950-control-run compsets at low and high resolution This PR brings in three new compsets: * A_WCYCL1950S_HR; * A_WCYCL1950S_LR; and * A_WCYCL1950S_LRtunedHR. In conjunction with this PR, new inputdata files have already been added to the svn server. We have tested that these new compsets run using short (day-long) simulations on cori-knl. It should be BFB for all other compsets [BFB]
./create_test --help
says (among other things):However, attempts to use one or more test suite names (e.g.,
prealpha
) results in the error:Either the documentation is incorrect or the code is not correct. It would be really convenient to be able to specify multiple test suites in one
create_test
call so all output is collected in one place.The text was updated successfully, but these errors were encountered: