[Avocado-devel] option --output-check-record behavior

[Marcos E. Matsunaga]

Hi All,

I am new to avocado and have just started to look into it.

I have been playing with avocado on Fedora 24 for a few weeks. I wrote a 
small script to run commands and was exploring the option 
"--output-check-record", but it never populate the files stderr.expected 
and stdout.expected. Instead, it prints an error with "[stderr]" in the 
job.log file. My understanding is that the output (stderr and stdout)  
of commands/scripts executed by avocado would be captured and saved on 
those files (like on synctest.py example), but it doesn't. I want to 
know if I am doing something wrong or it is a bug.

The script is very simple and the way I execute the command is:

cmd = ('/usr/sbin/xl create /VM/guest1/vm.cfg')
if utils.system(cmd) == "0":
       pass
else:
       return False

The command send to stdout:

Parsing config from /VM/guest1/vm.cfg

I run the test as:

avocado run --output-check-record all xentest.py

The job.log file contains:

2016-09-07 13:04:48,015 test             L0214 INFO | START 
1-/root/avocado-vt/io-fs-autotest-xen/xen/tests/xentest.py:xentest.test_xen_start_stop;1
2016-09-07 13:04:48,051 xentest          L0033 INFO | 
1-/root/avocado-vt/io-fs-autotest-xen/xen/tests/xentest.py:xentest.test_xen_start_stop;1: 
Running action create
2016-09-07 13:04:49,067 utils            L0151 ERROR| [stderr] Parsing 
config from /VM/guest1/vm.cfg
2016-09-07 13:04:49,523 test             L0586 INFO | PASS 
1-/root/avocado-vt/io-fs-autotest-xen/xen/tests/xentest.py:xentest.test_xen_start_stop;1

Thanks for your time and help.


-- 

Regards,

Marcos Eduardo Matsunaga

Oracle USA
Linux Engineering

“The statements and opinions expressed here are my own and do not
necessarily represent those of Oracle Corporation.”