Feature #2206
closed
osmo-gsm-tester should write to a log file, not only stdout
Added by neels about 7 years ago.
Updated over 6 years ago.
Description
For manual invocations, it does make sense to output the log on stdout, but that should only be in addition to an actual log file written to each run dir that is created to run tests in.
Add a logging target to osmo-gsm-tester.py for each run dir -- possibly in trial.py, and remove the logging target when such a trial run is done. Make sure that results of all suite runs are summarized at the end of a trial log before it is closed.
Added bonus: while the jenkins job runs and waits for osmo-gsm-tester to complete, run an ssh tail on the log file produced, so that we can see the test log continuously on the jenkins web site. (the old osmo-gsm-tester used to do that, IIRC.)
See class LogTarget in osmo_gsm_tester/log.py: A default log target to log to stdout is created on the line 197 by targets = [ LogTarget() ]. We should add another target to that list for each trial run. Maybe this needs explicit functions in log.py to add/remove a log target? (maybe not though.)
something like:
class Trial:
def __enter__(self):
self.log_target = LogTarget(output=self.log_file())
log.targets.append(self.log_target)
[...]
def __exit__(self,...):
[...]
log.targets.remove(self.log_target)
- Related to Feature #2205: osmo-gsm-tester should tell jenkins where to find test result files added
- Priority changed from High to Urgent
- Status changed from New to In Progress
- Assignee changed from 118 to neels
- % Done changed from 0 to 90
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
writes both a debug log file and a brief log file.
- Status changed from Resolved to Closed
Also available in: Atom
PDF
