Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: replace_with Sobin Thomas <sobin.thomas@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: kamil.konieczny@intel.com, dominik.karol.piatkowski@intel.com
Subject: [PATCH v2 i-g-t 1/1] tests/intel/xe_sysfs_scheduler: Add invalid string test for engine sysfs properties
Date: Mon, 31 Mar 2025 14:27:48 +0000	[thread overview]
Message-ID: <20250331142749.1821941-1-sobin.thomas@intel.com> (raw)

From: Sobin Thomas <sobin.thomas@intel.com>

This test validates that invalid string inputs are correctly rejected
by engine sysfs write. It ensures that the property values remain
unchanged when invalid inputs are provided.

v2: Added error check for return values for igt_sysfs_scanf and
igt_sysfs_printf. Removed the changes for fault injection in
tests/intel/xe_fault_injection.c

v1: Initial changes for checking error string.


Sobin Thomas (1):
  tests/intel/xe_sysfs_scheduler: Add invalid string test for engine
    sysfs properties

 tests/intel/xe_sysfs_scheduler.c | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)

Signed-off-by: Sobin Thomas <sobin.thomas@intel.com>
-- 
2.34.1


             reply	other threads:[~2025-03-31 14:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-31 14:27 replace_with Sobin Thomas [this message]
2025-03-31 14:27 ` [PATCH i-g-t 1/1] tests/intel/xe_sysfs_scheduler: Add invalid string test for engine sysfs properties replace_with Sobin Thomas
2025-04-01  9:44   ` Piatkowski, Dominik Karol
2025-04-01 13:21   ` Kamil Konieczny
2025-03-31 19:15 ` ✓ Xe.CI.BAT: success for series starting with [i-g-t,1/1] " Patchwork
2025-03-31 19:17 ` ✓ i915.CI.BAT: " Patchwork
2025-03-31 21:41 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-31 21:54 ` ✓ i915.CI.Full: success " Patchwork
2025-04-06 21:46 ` ✗ Xe.CI.Full: failure " Patchwork

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=20250331142749.1821941-1-sobin.thomas@intel.com \
    --to=sobin.thomas@intel.com \
    --cc=dominik.karol.piatkowski@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@intel.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