From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>,
Cleber Rosa <crosa@redhat.com>,
avocado-devel <avocado-devel@redhat.com>
Subject: Re: Avocado error fetching QEMU boot_linux.py assets
Date: Fri, 24 Jul 2020 07:56:02 +0200 [thread overview]
Message-ID: <7c12e791-ec29-809c-5ddf-30f3a14a4d6b@redhat.com> (raw)
In-Reply-To: <9173c3d6-df1f-b719-f124-fc6cf3ecb9f6@redhat.com>
On 7/24/20 7:43 AM, Philippe Mathieu-Daudé wrote:
> Hi,
>
> [cross list post]
>
> Using QEMU at commit 3cbc8970f5 I'm getting this error:
>
> Fetching assets from tests/acceptance/boot_linux_console.py.
> Fetching assets from tests/acceptance/boot_linux.py.
> Traceback (most recent call last):
> File "/usr/lib64/python3.7/runpy.py", line 193, in _run_module_as_main
> "__main__", mod_spec)
> File "/usr/lib64/python3.7/runpy.py", line 85, in _run_code
> exec(code, run_globals)
> File
> "/var/tmp/qemu-builddir/tests/venv/lib64/python3.7/site-packages/avocado/__main__.py",
> line 11, in <module>
> sys.exit(main.run())
> File
> "/var/tmp/qemu-builddir/tests/venv/lib64/python3.7/site-packages/avocado/core/app.py",
> line 91, in run
> return method(self.parser.config)
> File
> "/var/tmp/qemu-builddir/tests/venv/lib64/python3.7/site-packages/avocado/plugins/assets.py",
> line 291, in run
> success, fail = fetch_assets(test_file)
> File
> "/var/tmp/qemu-builddir/tests/venv/lib64/python3.7/site-packages/avocado/plugins/assets.py",
> line 200, in fetch_assets
> handler = FetchAssetHandler(test_file, klass, method)
> File
> "/var/tmp/qemu-builddir/tests/venv/lib64/python3.7/site-packages/avocado/plugins/assets.py",
> line 65, in __init__
> self.visit(self.tree)
> File "/usr/lib64/python3.7/ast.py", line 271, in visit
> return visitor(node)
> File "/usr/lib64/python3.7/ast.py", line 279, in generic_visit
> self.visit(item)
> File "/usr/lib64/python3.7/ast.py", line 271, in visit
> return visitor(node)
> File
> "/var/tmp/qemu-builddir/tests/venv/lib64/python3.7/site-packages/avocado/plugins/assets.py",
> line 139, in visit_ClassDef
> self.generic_visit(node)
> File "/usr/lib64/python3.7/ast.py", line 279, in generic_visit
> self.visit(item)
> File "/usr/lib64/python3.7/ast.py", line 271, in visit
> return visitor(node)
> File
> "/var/tmp/qemu-builddir/tests/venv/lib64/python3.7/site-packages/avocado/plugins/assets.py",
> line 171, in visit_Assign
> self.asgmts[cur_klass][cur_method][name] = node.value.s
> KeyError: 'launch_and_wait'
FYI here cur_klass='BootLinuxX8664' and name='chksum'.
>
> Same if I revert these:
> 0f26d94ec9 ("tests/acceptance: skip s390x_ccw_vrtio_tcg on GitLab")
> 1c80c87c8c ("tests/acceptance: refactor boot_linux to allow code reuse")
>
> If I remove boot_linux.py, all other files are processed correctly.
>
> Any idea what can be wrong here?
>
> Thanks,
>
> Phil.
>
prev parent reply other threads:[~2020-07-24 5:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 5:43 Avocado error fetching QEMU boot_linux.py assets Philippe Mathieu-Daudé
2020-07-24 5:56 ` Philippe Mathieu-Daudé [this message]
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=7c12e791-ec29-809c-5ddf-30f3a14a4d6b@redhat.com \
--to=philmd@redhat.com \
--cc=avocado-devel@redhat.com \
--cc=crosa@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).