test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "ohilyard@iol.unh.edu" <ohilyard@iol.unh.edu>,
	"dts@dpdk.org" <dts@dpdk.org>
Cc: "juraj.linkes@pantheon.tech" <juraj.linkes@pantheon.tech>
Subject: RE: [PATCH v1] framework: Move test-specific files to test directory
Date: Mon, 11 Apr 2022 02:40:15 +0000	[thread overview]
Message-ID: <001a2a80b577446f8ebaf237fc2fe0a8@intel.com> (raw)
In-Reply-To: <20220406141902.20334-1-ohilyard@iol.unh.edu>

>  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 ++++++------

I think qemu_libvirt, qemu_kvm, virt_resource should be considered too. 

Btw, What about the suites/modules which call/depend on these modules ?

      reply	other threads:[~2022-04-11  2:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 14:19 ohilyard
2022-04-11  2:40 ` Tu, Lijuan [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:

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

  git send-email \
    --in-reply-to=001a2a80b577446f8ebaf237fc2fe0a8@intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=juraj.linkes@pantheon.tech \
    --cc=ohilyard@iol.unh.edu \


* 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).