From: John Kacur <jkacur@redhat.com>
To: linux-rt-users@vger.kernel.org
Cc: Clark Williams <williams@redhat.com>, Tomas Glozar <tglozar@redhat.com>
Subject: [PATCH 2/6] rteval: Fix xmlout unit test XSL file path
Date: Fri, 17 Apr 2026 15:51:09 -0400 [thread overview]
Message-ID: <20260417195113.177799-3-jkacur@redhat.com> (raw)
In-Reply-To: <20260417195113.177799-1-jkacur@redhat.com>
The xmlout unit test was failing because it was looking for
rteval_text.xsl in the current directory, but the file is located
at rteval/rteval_text.xsl.
Update the test to use the correct path relative to the project root,
which is where the test is run from.
This fixes the test failure:
Before: 2 successful tests, 2 failed
After: 3 successful tests, 1 failed (only DMI test which needs root)
Signed-off-by: John Kacur <jkacur@redhat.com>
---
rteval/xmlout.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/rteval/xmlout.py b/rteval/xmlout.py
index 710d50a1fc0f..5ff426643c3a 100644
--- a/rteval/xmlout.py
+++ b/rteval/xmlout.py
@@ -283,7 +283,7 @@ def unit_test(rootdir):
print("------------- XML OUTPUT ----------------------------")
x.Write("-")
print("------------- XSLT PARSED OUTPUT --------------------")
- x.Write("-", "rteval_text.xsl")
+ x.Write("-", "rteval/rteval_text.xsl")
print("~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~")
x.Write("/tmp/xmlout-test.xml")
del x
@@ -294,7 +294,7 @@ def unit_test(rootdir):
print("------------- LOADED XML DATA --------------------------------")
x.Write("-")
print("------------- XSLT PARSED OUTPUT FROM LOADED XML--------------")
- x.Write("-", "rteval_text.xsl")
+ x.Write("-", "rteval/rteval_text.xsl")
x.close()
## Test new data parser ... it eats most data types
--
2.53.0
next prev parent reply other threads:[~2026-04-17 19:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 19:51 [PATCH 0/6] rteval: Improve CPU management infrastructure and add housekeeping option John Kacur
2026-04-17 19:51 ` [PATCH 1/6] rteval: Add cpuset module for cgroup v2 management John Kacur
2026-04-17 19:51 ` John Kacur [this message]
2026-04-17 19:51 ` [PATCH 3/6] rteval: Add CpuList class to cpulist_utils module John Kacur
2026-04-17 19:51 ` [PATCH 4/6] rteval: Migrate call sites to use CpuList class where beneficial John Kacur
2026-04-17 19:51 ` [PATCH 5/6] rteval: Add unit tests for CpuList class John Kacur
2026-04-17 19:51 ` [PATCH 6/6] rteval: Add --housekeeping option to reserve isolated CPUs John Kacur
2026-04-20 9:33 ` Tomas Glozar
2026-04-20 21:42 ` John Kacur
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=20260417195113.177799-3-jkacur@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