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

2016-09-14 Thread Ademar Reis
On Wed, Sep 14, 2016 at 05:27:03PM -0300, Ademar Reis wrote: > On Wed, Sep 14, 2016 at 06:54:31PM +0200, Lukáš Doktor wrote: > > Dne 9.9.2016 v 23:25 Lucas Meneghel Rodrigues napsal(a): > > > > > > > > > On Fri, Sep 9, 2016 at 8:14 AM Marcos E. Matsunaga > > > mailto:marcos.matsun...@oracle.com>>

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

2016-09-14 Thread Ademar Reis
On Wed, Sep 14, 2016 at 06:54:31PM +0200, Lukáš Doktor wrote: > Dne 9.9.2016 v 23:25 Lucas Meneghel Rodrigues napsal(a): > > > > > > On Fri, Sep 9, 2016 at 8:14 AM Marcos E. Matsunaga > > mailto:marcos.matsun...@oracle.com>> wrote: > > > > Hi guys, > > > > First of all, thanks again for

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

2016-09-14 Thread Lukáš Doktor
Dne 9.9.2016 v 23:25 Lucas Meneghel Rodrigues napsal(a): On Fri, Sep 9, 2016 at 8:14 AM Marcos E. Matsunaga mailto:marcos.matsun...@oracle.com>> wrote: Hi guys, First of all, thanks again for your help. I really appreciate it. I found an interesting behavior. If I set loglevel=in

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

2016-09-14 Thread Marcos E. Matsunaga
I filed a bug (I hope it is in the right place). https://github.com/avocado-framework/avocado-vt/issues/701 Thanks On 14/09/16 17:44, Lukáš Doktor wrote: Dne 9.9.2016 v 23:30 Lucas Meneghel Rodrigues napsal(a): On Fri, Sep 9, 2016 at 8:14 AM Marcos E. Matsunaga mailto:marcos.matsun...@ora

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

2016-09-14 Thread Lukáš Doktor
Dne 9.9.2016 v 23:30 Lucas Meneghel Rodrigues napsal(a): On Fri, Sep 9, 2016 at 8:14 AM Marcos E. Matsunaga mailto:marcos.matsun...@oracle.com>> wrote: Hi guys, First of all, thanks again for your help. I really appreciate it. I found an interesting behavior. If I set loglevel=in

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

2016-09-09 Thread Lucas Meneghel Rodrigues
On Fri, Sep 9, 2016 at 8:14 AM Marcos E. Matsunaga < marcos.matsun...@oracle.com> wrote: > Hi guys, > > First of all, thanks again for your help. I really appreciate it. > > I found an interesting behavior. If I set loglevel=info in > /etc/avocado/avocado.conf, it will not produce any content in >

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

2016-09-09 Thread Lucas Meneghel Rodrigues
On Fri, Sep 9, 2016 at 8:14 AM Marcos E. Matsunaga < marcos.matsun...@oracle.com> wrote: > Hi guys, > > First of all, thanks again for your help. I really appreciate it. > > I found an interesting behavior. If I set loglevel=info in > /etc/avocado/avocado.conf, it will not produce any content in >

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

2016-09-09 Thread Marcos E. Matsunaga
Hi guys, First of all, thanks again for your help. I really appreciate it. I found an interesting behavior. If I set loglevel=info in /etc/avocado/avocado.conf, it will not produce any content in stderr.expected and stdout.expected. If I set loglevel=debug, then it will work as it should. I d

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

2016-09-08 Thread Amador Segundo
On Sep 8, 2016 9:02 PM, "Lucas Meneghel Rodrigues" wrote: > > By the way, you *must* set shell=True to use pipes (which I did forget). Otherwise the pipes won't work. Yes, or that! :) > > On Thu, Sep 8, 2016 at 4:00 PM Lucas Meneghel Rodrigues wrote: >> >> I think you guys are missing the point

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

2016-09-08 Thread Lucas Meneghel Rodrigues
Yep, that was the problem. The pipe won't work if shell=False (default). Now, on the rationale why shell=False is the default, basically, it's unsafe, see: https://docs.python.org/2/library/subprocess.html With shell=True, the expected standard output starts to appear. On Thu, Sep 8, 2016 at 4:

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

2016-09-08 Thread Lucas Meneghel Rodrigues
By the way, you *must* set shell=True to use pipes (which I did forget). Otherwise the pipes won't work. On Thu, Sep 8, 2016 at 4:00 PM Lucas Meneghel Rodrigues wrote: > I think you guys are missing the point here. I just tried Marcos's test > here and that's what I get with Avocado LTS 36.2: >

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

2016-09-08 Thread Lucas Meneghel Rodrigues
I think you guys are missing the point here. I just tried Marcos's test here and that's what I get with Avocado LTS 36.2: $ avocado run xentest.py --output-check-record all JOB ID : c44d95698bc6a20329691a9c10370c3b63c8944f JOB LOG: /home/lmr/avocado/job-results/job-2016-09-08T15.54-c44d956

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

2016-09-08 Thread Marcos E. Matsunaga
Thanks Amador, I assumed it would have the same behavior as utils.system and completely ignored the pipe. On 09/08/2016 07:39 PM, Amador Segundo wrote: On Sep 8, 2016 8:19 PM, "Marcos E. Matsunaga" mailto:marcos.matsun...@oracle.com>> wrote: > > Hi Cleber, > > Sorry for being a pain. I'v

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

2016-09-08 Thread Amador Segundo
On Sep 8, 2016 8:19 PM, "Marcos E. Matsunaga" wrote: > > Hi Cleber, > > Sorry for being a pain. I've tried to use process.system to execute commands, but I got an error, that's why I kept the autotest libraries (I actually copied from one of the files in io-github-autotest-libvirt). > > The error

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

2016-09-08 Thread Marcos E. Matsunaga
Hi Cleber, Sorry for being a pain. I've tried to use process.system to execute commands, but I got an error, that's why I kept the autotest libraries (I actually copied from one of the files in io-github-autotest-libvirt). The error I'm getting is: 2016-09-08 13:49:25,844 sysinfo L0

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

2016-09-08 Thread Cleber Rosa
On 09/08/2016 01:50 PM, Marcos E. Matsunaga wrote: > > On 09/08/2016 05:44 PM, Cleber Rosa wrote: >> On 09/08/2016 11:34 AM, Marcos E. Matsunaga wrote: >>> Hi Cleber, >>> >>> Thanks for your quick reply. That's exactly what I understood, but here >>> is what is happening >>> >>> I have a directory

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

2016-09-08 Thread Marcos E. Matsunaga
On 09/08/2016 05:44 PM, Cleber Rosa wrote: On 09/08/2016 11:34 AM, Marcos E. Matsunaga wrote: Hi Cleber, Thanks for your quick reply. That's exactly what I understood, but here is what is happening I have a directory ~/avocado/xen/tests where I have the xentest.py script. When I execute it, i

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

2016-09-08 Thread Cleber Rosa
On 09/08/2016 11:34 AM, Marcos E. Matsunaga wrote: > Hi Cleber, > > Thanks for your quick reply. That's exactly what I understood, but here > is what is happening > > I have a directory ~/avocado/xen/tests where I have the xentest.py > script. When I execute it, it does create the directory > ~/

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

2016-09-08 Thread Marcos E. Matsunaga
Hi Cleber, Thanks for your quick reply. That's exactly what I understood, but here is what is happening I have a directory ~/avocado/xen/tests where I have the xentest.py script. When I execute it, it does create the directory ~/avocado/xen/tests/xentest.py.data with stderr.expected and std

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

2016-09-08 Thread Cleber Rosa
On 09/08/2016 10:25 AM, Marcos E. Matsunaga wrote: > 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

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

2016-09-08 Thread 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. I