canonical-certification-server output is too verbose
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Checkbox |
Fix Released
|
Medium
|
Sylvain Pineau | ||
Bug Description
Installed canonical-
Selected the Server-cert suite from the suite selection list.
Once I hit enter on OK, it started running jobs and dumping VERY verbose output to screen.
For now, as we're still in development, that's ok, but for release, this REALLY needs to be quieted down.
The verbose output is great for a log file... or when called for via a --verbose flag of some sort, but for a generic, ordinary test run, the output should be far more terse. I would only really want to see something like this:
Running job FOO
Result of Job FOO: PASS
Running Job BAR
Result of Job BAR: FAIL
Or more simply:
Job FOO: PASS
Job BAR: FAIL
<OUTPUT of job BAR> **
** maybe include the output of the job for fail cases, maybe not... perhaps it's enough to just log them and at the end of the run say "One or more jobs failed, see $LOGFILE for more details"
As it is right now, the UI is way too nosiy during execution and could be confusing and difficult to follow.
BUT, it's WAY FREAKING COOL!
Related branches
- Sylvain Pineau (community): Approve
- Zygmunt Krynicki (community): Approve
-
Diff: 802 lines (+425/-231)1 file modifiedcheckbox-ng/checkbox_ng/commands/cli.py (+425/-231)
| Changed in checkbox: | |
| importance: | Undecided → Medium |
| status: | New → In Progress |
| assignee: | nobody → Sylvain Pineau (sylvain-pineau) |
| Samantha Jian-Pielak (samantha-jian) wrote | #1 |
| Sylvain Pineau (sylvain-pineau) wrote | #2 |
| Changed in checkbox: | |
| status: | In Progress → Fix Committed |
| milestone: | none → plainbox-0.5 |
| Changed in checkbox: | |
| status: | Fix Committed → Fix Released |
Please keep 'Running job: FOO' there, it helps for testers to know it's still running especially for cpu/stress and memory/check so that they don't ctrl-c out in the middle of the testing. The test description isn't mentioned in this bug, but in the cpu stress test case, it gives good indication for the test duration. Please keep it as well.