From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: "ohilyard@iol.unh.edu" <ohilyard@iol.unh.edu>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "lijuan.tu@intel.com" <lijuan.tu@intel.com>
Subject: RE: [PATCH v2 1/2] framework: Move test-specific files to test directory
Date: Wed, 13 Apr 2022 07:25:23 +0000 [thread overview]
Message-ID: <cd44ba0b24c7485fa5596457c77f9a0b@pantheon.tech> (raw)
In-Reply-To: <20220411175549.14680-1-ohilyard@iol.unh.edu>
> ---
> framework/flow/__init__.py | 0
> framework/virt_resource.py | 2 +-
> tests/data/__init__.py | 2 ++
> tests/util/__init__.py | 2 ++
> tests/util/flow/__init__.py | 2 ++
> {framework => tests/util}/flow/enums.py | 0
> {framework => tests/util}/flow/exceptions.py | 0
> {framework => tests/util}/flow/flow.py | 0
> {framework => tests/util}/flow/flow_action_items.py | 0
> {framework => tests/util}/flow/flow_items.py | 8 +++-----
> {framework => tests/util}/flow/flow_pattern_items.py | 0
> {framework => tests/util}/flow/flow_rule.py | 2 +-
> {framework => tests/util}/flow/generator.py | 0
> tests/util/virt/__init__.py | 2 ++
> {framework => tests/util/virt}/virt_base.py | 8 ++++----
> {framework => tests/util/virt}/virt_common.py | 8 ++++----
> {framework => tests/util/virt}/virt_dut.py | 10 +++++-----
> {framework => tests/util/virt}/virt_scene.py | 12 ++++++------
As Lijian Mentioned, we should also move qemu_kvm and qemu_libvirt. As far as I can tell, the only virt file that needs to stay is virt_resource and all of the rest (including qemu) can be moved.
next prev parent reply other threads:[~2022-04-13 7:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 17:55 ohilyard
2022-04-11 17:55 ` [PATCH v2 2/2] update files depending on tests/util ohilyard
2022-04-11 17:57 ` Owen Hilyard
2022-04-13 7:28 ` Juraj Linkeš
2022-04-13 12:50 ` Owen Hilyard
2022-04-13 7:25 ` Juraj Linkeš [this message]
2022-04-13 12:50 ` [PATCH v2 1/2] framework: Move test-specific files to test directory Owen Hilyard
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=cd44ba0b24c7485fa5596457c77f9a0b@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=dts@dpdk.org \
--cc=lijuan.tu@intel.com \
--cc=ohilyard@iol.unh.edu \
/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).