public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: Tomas Glozar <tglozar@redhat.com>
Cc: Clark Williams <williams@redhat.com>,
	 Linux RT Users <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH 1/2] rteval: Move unittest.py to tests/unittest-legacy.py
Date: Tue, 25 Nov 2025 14:04:33 -0500 (EST)	[thread overview]
Message-ID: <7bd18465-259f-aa29-8ce6-da923666734e@redhat.com> (raw)
In-Reply-To: <20251125110241.277542-1-tglozar@redhat.com>



On Tue, 25 Nov 2025, Tomas Glozar wrote:

> We now have a tests/ folder. Move unittest.py there, rename it to
> unittest-legacy.py to prevent conflict with Python's unittest
> module, and remove the now empty directory unit-tests/.
> 
> Signed-off-by: Tomas Glozar <tglozar@redhat.com>
> ---
> This is a follow-up to [1], in place of patch 2 and 3. Patch 1 got applied,
> patches 2 and 3 required changes following the merging of [2].
> 
> [1] https://lore.kernel.org/linux-rt-users/20251107134749.257350-1-tglozar@redhat.com/T/
> [2] https://lore.kernel.org/linux-rt-users/20251107182645.19545-1-jkacur@redhat.com/T/
> 
>  unit-tests/unittest.py => tests/unittest-legacy.py | 0
>  1 file changed, 0 insertions(+), 0 deletions(-)
>  rename unit-tests/unittest.py => tests/unittest-legacy.py (100%)
> 
> diff --git a/unit-tests/unittest.py b/tests/unittest-legacy.py
> similarity index 100%
> rename from unit-tests/unittest.py
> rename to tests/unittest-legacy.py
> -- 
> 2.51.1
> 
> 
Signed-off-by: John Kacur <jkacur@redghat.com>


      parent reply	other threads:[~2025-11-25 19:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25 11:02 [PATCH 1/2] rteval: Move unittest.py to tests/unittest-legacy.py Tomas Glozar
2025-11-25 11:02 ` [PATCH 2/2] rteval: Add README-tests Tomas Glozar
2025-11-25 19:05   ` John Kacur
2025-11-25 19:04 ` John Kacur [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=7bd18465-259f-aa29-8ce6-da923666734e@redhat.com \
    --to=jkacur@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglozar@redhat.com \
    --cc=williams@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