Opened 8 years ago
Closed 4 years ago
#135 closed defect (fixed)
Typo in test_cpu.info
| Reported by: | Owned by: | Eric Swenson | |
|---|---|---|---|
| Priority: | trivial | Milestone: | MR12.8 |
| Component: | Documentation | Version: | MR12.7 |
| Keywords: | test_c[u | Cc: |
Description
The info page reads:
-exclude LIST, -excl LIST excludes tests specified in the LIST, where LIST can be either a valid test number or a name. -exclude TEST_LIST, -excl TEST_LIST excludes the tests identified by TEST_LIST, where TEST_LIST is either a set of test names or numbers, from the tests that are run.
Either one of the entries should be deleted, or they should be merged.
Change History (5)
comment:1 by , 7 years ago
comment:2 by , 5 years ago
The appropriate method for describing operands of -excluded is something like the following...
-exclude TEST ... TEST, -excl TEST ... TEST excludes the specified tests from being run. TEST may be: the name of one of the tests in "List of requests for diagnostic tests" section below; or the number of the test to be excluded where test numbers are displayed by the command: test_cpu -test_names
comment:5 by , 4 years ago
| Milestone: | → MR12.8 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
| Version: | → MR12.7 |
Note:
See TracTickets
for help on using tickets.
The documentation has this expressed the same way. I agree it is confusing, but I'm not sure which is better, to change the first --exclude to use TEST_NAME and have TEST_NAME documented (as it currently is to reflect a single test); and then include both usages, or whether it is better to have one --exclude with a parameter that is documented as being either a single test or a list of tests.