qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Kevin Wolf <kwolf@redhat.com>, Thomas Huth <thuth@redhat.com>
Cc: den@openvz.org, jsnow@redhat.com, qemu-devel@nongnu.org,
	qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [PATCH v4 9/9] iotests: rename and move 169 and 199 tests
Date: Tue, 19 May 2020 14:32:59 +0300	[thread overview]
Message-ID: <2dfeb643-bbb2-d50b-d14c-ea2db04aa3c5@virtuozzo.com> (raw)
In-Reply-To: <20200519090709.GC7652@linux.fritz.box>

19.05.2020 12:07, Kevin Wolf wrote:
> Am 18.05.2020 um 18:12 hat Thomas Huth geschrieben:
>> On 15/05/2020 23.15, Vladimir Sementsov-Ogievskiy wrote:
>>> Rename bitmaps migration tests and move them to tests subdirectory to
>>> demonstrate new human-friendly test naming.
>>>
>>> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
>>> ---
>>>   tests/qemu-iotests/{199 => tests/migrate-bitmaps-postcopy-test}   | 0
>>>   .../{199.out => tests/migrate-bitmaps-postcopy-test.out}          | 0
>>>   tests/qemu-iotests/{169 => tests/migrate-bitmaps-test}            | 0
>>>   tests/qemu-iotests/{169.out => tests/migrate-bitmaps-test.out}    | 0
>>>   4 files changed, 0 insertions(+), 0 deletions(-)
>>>   rename tests/qemu-iotests/{199 => tests/migrate-bitmaps-postcopy-test} (100%)
>>>   rename tests/qemu-iotests/{199.out => tests/migrate-bitmaps-postcopy-test.out} (100%)
>>>   rename tests/qemu-iotests/{169 => tests/migrate-bitmaps-test} (100%)
>>>   rename tests/qemu-iotests/{169.out => tests/migrate-bitmaps-test.out} (100%)
>>>
>>> diff --git a/tests/qemu-iotests/199 b/tests/qemu-iotests/tests/migrate-bitmaps-postcopy-test
>>> similarity index 100%
>>> rename from tests/qemu-iotests/199
>>> rename to tests/qemu-iotests/tests/migrate-bitmaps-postcopy-test
>>> diff --git a/tests/qemu-iotests/199.out b/tests/qemu-iotests/tests/migrate-bitmaps-postcopy-test.out
>>> similarity index 100%
>>> rename from tests/qemu-iotests/199.out
>>> rename to tests/qemu-iotests/tests/migrate-bitmaps-postcopy-test.out
>>> diff --git a/tests/qemu-iotests/169 b/tests/qemu-iotests/tests/migrate-bitmaps-test
>>> similarity index 100%
>>> rename from tests/qemu-iotests/169
>>> rename to tests/qemu-iotests/tests/migrate-bitmaps-test
>>> diff --git a/tests/qemu-iotests/169.out b/tests/qemu-iotests/tests/migrate-bitmaps-test.out
>>> similarity index 100%
>>> rename from tests/qemu-iotests/169.out
>>> rename to tests/qemu-iotests/tests/migrate-bitmaps-test.out
>>
>> I like the idea ... but the path name + file names get now quite long.
>> While you're at it, what about renaming the "qemu-iotests" directory to
>> just "iotests" or even just "io" now?
> 
> Renames are always kind of painful. Do we have a real reason for the
> rename except that the paths feel a bit long subjectively?
> 
> Of course, if we're renaming all files anyway, changing the directory
> name at the same time shouldn't give any additional pain, so it would be
> completely reasonable then. We're not renaming the test harness files,
> though, and even only two test cases in this patch.
> 
> Maybe this final patch should stay RFC until we have the infrastructure
> in and then we can have a single series that moves all tests and also
> renames the directory? Maybe a not strictly necessary rename of the
> tooling would be bearable in the context of a mass rename of tests.
> 

I'm absolutely not hurrying about this thing. And actual aim of the series is another. I even doubt that we will mass rename the tests: who knows what they all test?) I don't. Still we may rename some tests, and we'll create new named tests which is good enough.. OK, if I resend a new version, I'll add an RFC patch on renaming the directory, up to maintainers, take it now or not :)

-- 
Best regards,
Vladimir


  reply	other threads:[~2020-05-19 11:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 21:14 [PATCH v4 0/9] Rework iotests/check Vladimir Sementsov-Ogievskiy
2020-05-15 21:14 ` [PATCH v4 1/9] iotests/277: use dot slash for nbd-fault-injector.py running Vladimir Sementsov-Ogievskiy
2020-05-15 21:14 ` [PATCH v4 2/9] iotests: fix some whitespaces in test output files Vladimir Sementsov-Ogievskiy
2020-05-15 21:14 ` [PATCH v4 3/9] iotests/283: make executable Vladimir Sementsov-Ogievskiy
2020-05-15 21:15 ` [PATCH v4 4/9] iotests: define group in each iotest Vladimir Sementsov-Ogievskiy
2020-05-15 21:15 ` [PATCH v4 5/9] iotests: add findtests.py Vladimir Sementsov-Ogievskiy
2020-05-15 21:15 ` [PATCH v4 6/9] iotests: add testenv.py Vladimir Sementsov-Ogievskiy
2020-05-15 21:15 ` [PATCH v4 7/9] iotests: add testrunner.py Vladimir Sementsov-Ogievskiy
2020-05-15 21:15 ` [PATCH v4 8/9] iotests: rewrite check into python Vladimir Sementsov-Ogievskiy
2020-05-15 21:15 ` [PATCH v4 9/9] iotests: rename and move 169 and 199 tests Vladimir Sementsov-Ogievskiy
2020-05-18 16:12   ` Thomas Huth
2020-05-18 17:33     ` Vladimir Sementsov-Ogievskiy
2020-05-19  9:07     ` Kevin Wolf
2020-05-19 11:32       ` Vladimir Sementsov-Ogievskiy [this message]
2020-05-19 11:41         ` Kevin Wolf
2020-05-21 18:32           ` John Snow
2020-05-27 18:50             ` Vladimir Sementsov-Ogievskiy
2020-05-29 19:37               ` John Snow
2020-06-20 15:38 ` [PATCH v4 0/9] Rework iotests/check Vladimir Sementsov-Ogievskiy

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=2dfeb643-bbb2-d50b-d14c-ea2db04aa3c5@virtuozzo.com \
    --to=vsementsov@virtuozzo.com \
    --cc=den@openvz.org \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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).