Opened 11 years ago
Closed 11 years ago
#5959 closed Bugs (invalid)
Getting a full test log (log-level=all) depends on the argument order
| Reported by: | Owned by: | Gennadiy Rozental | |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | test |
| Version: | Boost Development Trunk | Severity: | Problem |
| Keywords: | test, log, testlog, log-level | Cc: |
Description
When using Boost.Test it depends on the argument order if I can get a full test log or not. log-level is set to "all" in both cases, but note the changed argument order.
test --report_level=no --output_format=XML --log-level=all (test log only for failing tests)
test --log_level=all --output_format=XML --report_level=no (works - full test log)
Noticed when using 1.40.0 but reproduced with trunk.
Change History (2)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I just realized, it was not the wrong argument order, but using the argument "log-level" (dash) instead of log_level (underscore).
I`m embarrassed.
Sorry.