qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Cleber Rosa <crosa@redhat.com>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Eduardo Habkost" <ehabkost@redhat.com>,
	qemu-devel@nongnu.org, "Lukáš Doktor" <ldoktor@redhat.com>,
	"Fam Zheng" <famz@redhat.com>,
	"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH v2 0/6] Avocado: start multi-arch tests, add a Travis job
Date: Thu, 28 Jun 2018 18:13:35 +0100	[thread overview]
Message-ID: <87efgqvnpc.fsf@linaro.org> (raw)
In-Reply-To: <8f45f2f0-0e3e-7b0d-ff92-9fd21f1cb8f7@redhat.com>


Cleber Rosa <crosa@redhat.com> writes:

> On 06/28/2018 11:46 AM, Alex Bennée wrote:
>>
>> Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
>>
>>> Hi,
>>>
>>> Another neanderthal approach to add multi-arch acceptance tests using
>>> Avocado.
>>>
>>> Since Cleber Rosa work got merged [0], I can restart my previous attempt [1]
>>> at using Avocado in QEMU.
>>> Cleber Rosa rewrote my previous v1 [1], in good python, now this v2 pushes
>>> a bit further:
>>> - we can now run other archs
>>> - Avocado is integrated into Travis CI
>>>
>>> I'm not sure Travis is the best CI available for those tests, but it runs
>>> quite fast:
>>>
>>>       ...
>>>       LINK    x86_64-softmmu/qemu-system-x86_64
>>>     JOB ID     : a3a56af3c02d193e862ce660aae1d9c72926dcb6
>>>     JOB LOG    : /home/travis/avocado/job-results/job-2018-06-21T23.49-a3a56af/job.log
>>>      (1/7) tests/acceptance/boot_linux_console.py:BootLinuxConsoleX86_64.test:  PASS (3.89 s)
>>>      (2/7) tests/acceptance/boot_linux_console.py:BootLinuxConsoleMips.test:  PASS (1.83 s)
>>>      (3/7) tests/acceptance/version.py:Version.test_qmp_human_info_version:  PASS (0.05 s)
>>>      (4/7) tests/acceptance/vnc.py:Vnc.test_no_vnc:  PASS (0.04 s)
>>>      (5/7) tests/acceptance/vnc.py:Vnc.test_no_vnc_change_password:  PASS (0.04 s)
>>>      (6/7) tests/acceptance/vnc.py:Vnc.test_vnc_change_password_requires_a_password:  PASS (0.05 s)
>>>      (7/7) tests/acceptance/vnc.py:Vnc.test_vnc_change_password:  PASS (0.05 s)
>>>     RESULTS    : PASS 7 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0
>>>     JOB TIME   : 6.21 s
>>
>> Hmm however if I do:
>>
>>    pip install --user avocado-framework
>>    avocado run tests/acceptance
>>
>> I get:
>>
>>    Failed to load plugin from module "avocado_vt.plugins.vt_list": ImportError('No module named netaddr',)
>>    Failed to load plugin from module "avocado_vt.plugins.vt": ImportError('No module named netaddr',)
>>    Failed to load plugin from module "avocado_vt.plugins.vt_bootstrap": OSError(13, 'Permission denied')
>
> Alex,
>
> These are errors related to your installation of Avocado-*VT*[1].
>
>>    Error running method "run" of plugin "virt": 'Namespace' object has no attribute 'default_avocado_params'
>>    Avocado crashed unexpectedly: [Errno 13] Permission denied: '/var/lib/libvirt/images/avocado_sg6NRi'
>>    You can find details in /var/tmp/avocado-traceback-2018-06-28_16:44:25-DGb1CG.log
>>
>
> And these from Avocado-*Virt*[2].  Neither of those are used in the
> tests under "tests/acceptance".
>
>> Which I seem to remember from last time I looked into this. I think
>> avocado makes a bunch of assumptions about the filesystem and OS layout
>> which is hard to gloss over for something you should be able to run
>> straight out of the source tree.
>>
>>
>
> These Avocado-*VT* issues deserve a better look indeed.  Would you
> please describe (if not here, under a GH issue) your environment?

Ahh probably from last time I tried to get things up and running. I
rm -rf ~/.local and things seem to be working well now.

However I was under the impression that VT or virt was needed for this
testing. Or is this an old assumption?

>
> Thanks,
> - Cleber.
>
> [1] - https://github.com/avocado-framework/avocado-vt
> [2] - https://github.com/avocado-framework/avocado-virt
>
>>>
>>>     Done. Your build exited with 0.
>>>
>>>     Job ran for 5 min 34 sec
>>>
>>> I couldn't add the Alpha tests because all the vmlinux kernels I found
>>> online are gzipped, so I'm waiting some upstream Avocado merges before.
>>>
>>> Cleber: I hope you can help me pythonizing this series :p
>>>
>>> Regards,
>>>
>>> Phil.
>>>
>>> [0]: http://lists.nongnu.org/archive/html/qemu-devel/2018-06/msg04531.html
>>> [1]: http://lists.nongnu.org/archive/html/qemu-devel/2018-04/msg03076.html
>>>
>>> Philippe Mathieu-Daudé (6):
>>>   avocado: Add a Test.arch property
>>>   tests/acceptance: Rename the x86-64 specific BootLinuxConsole test
>>>   tests/acceptance: Improve the Avocado tags
>>>   tests/acceptance: Add a BootLinuxConsoleMips test
>>>   tests/acceptance: Add a kludge to not use the default console
>>>   travis: Add Avocado tests
>>>
>>>  .travis.yml                               |  8 +++++
>>>  scripts/qemu.py                           |  6 ++--
>>>  tests/acceptance/avocado_qemu/__init__.py | 17 ++++++---
>>>  tests/acceptance/boot_linux_console.py    | 44 +++++++++++++++++++++--
>>>  4 files changed, 67 insertions(+), 8 deletions(-)
>>
>>
>> --
>> Alex Bennée
>>


--
Alex Bennée

  reply	other threads:[~2018-06-28 17:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22  0:44 [Qemu-devel] [PATCH v2 0/6] Avocado: start multi-arch tests, add a Travis job Philippe Mathieu-Daudé
2018-06-22  0:44 ` [Qemu-devel] [RFC PATCH v2 1/6] avocado: Add a Test.arch property Philippe Mathieu-Daudé
2018-06-28 16:10   ` Alex Bennée
2018-06-28 21:54     ` Alex Bennée
2018-06-28 22:03       ` Philippe Mathieu-Daudé
2018-07-27  5:35         ` Philippe Mathieu-Daudé
2018-06-22  0:44 ` [Qemu-devel] [PATCH v2 2/6] tests/acceptance: Rename the x86-64 specific BootLinuxConsole test Philippe Mathieu-Daudé
2018-06-28 17:17   ` Alex Bennée
2018-06-22  0:44 ` [Qemu-devel] [PATCH v2 3/6] tests/acceptance: Improve the Avocado tags Philippe Mathieu-Daudé
2018-06-22  0:44 ` [Qemu-devel] [PATCH v2 4/6] tests/acceptance: Add a BootLinuxConsoleMips test Philippe Mathieu-Daudé
2018-06-28 16:23   ` Alex Bennée
2018-06-28 17:40     ` Philippe Mathieu-Daudé
2018-06-28 18:36       ` Alex Bennée
2018-06-28 22:45         ` Philippe Mathieu-Daudé
2018-07-04 19:56           ` Philippe Mathieu-Daudé
2018-07-04 20:47             ` Eduardo Habkost
2018-07-04 21:44               ` Philippe Mathieu-Daudé
2018-07-04 22:32                 ` Eduardo Habkost
2018-06-22  0:44 ` [Qemu-devel] [RFC PATCH v2 5/6] tests/acceptance: Add a kludge to not use the default console Philippe Mathieu-Daudé
2018-06-28 16:33   ` Alex Bennée
2018-06-22  0:44 ` [Qemu-devel] [PATCH v2 6/6] travis: Add Avocado tests Philippe Mathieu-Daudé
2018-06-28 15:46 ` [Qemu-devel] [PATCH v2 0/6] Avocado: start multi-arch tests, add a Travis job Alex Bennée
2018-06-28 16:26   ` Cleber Rosa
2018-06-28 17:13     ` Alex Bennée [this message]
2018-06-28 17:24       ` Philippe Mathieu-Daudé
2018-06-28 16:01 ` Alex Bennée
2018-07-27  5:33   ` Philippe Mathieu-Daudé
2018-07-27 16:30     ` Alex Bennée

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87efgqvnpc.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=aurelien@aurel32.net \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=famz@redhat.com \
    --cc=ldoktor@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).