From: Pranay Samala <pranay.samala@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: karthik.b.s@intel.com, sameer.lattannavar@intel.com,
pranay.samala@intel.com
Subject: [PATCH i-g-t 0/3] Fix incorrect skips and improve cleanup
Date: Wed, 29 Apr 2026 15:09:52 +0530 [thread overview]
Message-ID: <20260429093955.3726263-1-pranay.samala@intel.com> (raw)
This series fixes issues where tests were being skipped
incorrectly and cleanup was not always happening.
Capability checks were earlier done outside dynamic subtests,
which could cause valid cases to be skipped if a later output
checks fails. Move these checks inside igt_dynamic_f() to ensure
each case runs independently.
Cleanup is also improved by centralizing framebuffer handling
and calling test_fini() after each dynamic subtest, so resources
are always released even on early exits.
Pranay Samala (3):
tests/kms_hdr: Move framebuffer into data_t for centralized cleanup
tests/kms_hdr: Move test_fini() for proper cleanup
tests/kms_hdr: Move capability checks inside dynamic subtests
tests/kms_hdr.c | 207 +++++++++++++++++++++---------------------------
1 file changed, 90 insertions(+), 117 deletions(-)
--
2.34.1
next reply other threads:[~2026-04-29 9:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 9:39 Pranay Samala [this message]
2026-04-29 9:39 ` [PATCH i-g-t 1/3] tests/kms_hdr: Move framebuffer into data_t for centralized cleanup Pranay Samala
2026-05-04 9:37 ` Karthik B S
2026-04-29 9:39 ` [PATCH i-g-t 2/3] tests/kms_hdr: Move test_fini() for proper cleanup Pranay Samala
2026-05-04 9:39 ` Karthik B S
2026-04-29 9:39 ` [PATCH i-g-t 3/3] tests/kms_hdr: Move capability checks inside dynamic subtests Pranay Samala
2026-05-04 9:40 ` Karthik B S
2026-04-29 14:02 ` ✓ i915.CI.BAT: success for Fix incorrect skips and improve cleanup Patchwork
2026-04-29 14:06 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-29 23:31 ` ✗ i915.CI.Full: failure " Patchwork
2026-04-29 23:51 ` ✗ Xe.CI.FULL: " 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=20260429093955.3726263-1-pranay.samala@intel.com \
--to=pranay.samala@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=karthik.b.s@intel.com \
--cc=sameer.lattannavar@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