Red Hat Bugzilla – Bug 1010756
[RFE] feature for rlRun, output the command and stdout stderr to "t_log--$caseName"
Last modified: 2017-12-05 23:00:14 EST
Created attachment 801458 [details]
patch for complete
Description of problem:
RFE: feature for rlRun, output the command and stdout stderr to OUTPUTFILE and t_log--$caseName
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. cur rlRun did not output the command line info to OUTPUTFILE and t_log--$caseName;
2. sometimes we want to skip the exit code check.
rlRun "CMD no need check exit code, need screen info" -
[21:14:47 root@ /tmp/tmp.X3Cr127p1l]# CMD no need check exit code,
the out put of CMD
I'm not entirely sure about this RFE. For the OUTPUTFILE part, I'll need to look into how we use (or don't) OUTPUTFILE elsewhere, and if it is supposed to be always set in BL test.
I like the 'don't check exit code, just log" part though, so I'll try to think of something.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Do you still need this feature? Why rlRun -s "command" 0-255 or rlRun -s "command; :" is not enough?
(In reply to Dalibor Pospíšil from comment #5)
> Do you still need this feature? Why rlRun -s "command" 0-255 or rlRun -s
> "command; :" is not enough?
No, sometimes we don't want the end check log,
and just ":: [ BEGIN ] :: Running " is not enough.
$ rlRun -s "ls"
:: [ BEGIN ] :: Running 'ls'
:: [ PASS ] :: Command 'ls' (Expected 0, got 0)
$ run 'ls'
[09:32:35 yjh@ ~~]# ls
:: [ PASS ] :: Running 'ls' (Expected 0, got 0)
$ run 'ls' -
[09:32:38 yjh@ ~~]# ls
<<<--- here no PASS/WARN/FAIL check and log report