From: Vinod Govindapillai <vinod.govindapillai@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: vinod.govindapillai@intel.com, santhosh.reddy.guddati@intel.com,
jani.saarinen@intel.com
Subject: [PATCH i-g-t v1] tests/intel/kms_fbc_dirty_rect: fix the log level in fbc enabled check
Date: Wed, 5 Mar 2025 12:32:07 +0200 [thread overview]
Message-ID: <20250305103207.137714-1-vinod.govindapillai@intel.com> (raw)
Even if FBC is enabled and test is successfull, using warn level
to print the info will make the CI treat this as a failure. In
case FBC is not enabled, the assert will be triggered and print
the error case.
Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
---
tests/intel/kms_fbc_dirty_rect.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/intel/kms_fbc_dirty_rect.c b/tests/intel/kms_fbc_dirty_rect.c
index 1e3fc1d33..ea7a73124 100644
--- a/tests/intel/kms_fbc_dirty_rect.c
+++ b/tests/intel/kms_fbc_dirty_rect.c
@@ -130,7 +130,7 @@ set_fb_and_collect_crc(data_t *data, igt_plane_t *plane, struct igt_fb *fb,
igt_pipe_crc_get_current(data->drm_fd, data->pipe_crc, crc);
igt_pipe_crc_stop(data->pipe_crc);
igt_assert_f(intel_fbc_is_enabled(data->drm_fd, data->pipe,
- IGT_LOG_WARN),
+ IGT_LOG_INFO),
"FBC is not enabled\n");
}
--
2.43.0
next reply other threads:[~2025-03-05 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 10:32 Vinod Govindapillai [this message]
2025-03-06 5:06 ` ✓ Xe.CI.BAT: success for tests/intel/kms_fbc_dirty_rect: fix the log level in fbc enabled check Patchwork
2025-03-06 5:25 ` ✓ i915.CI.BAT: " Patchwork
2025-03-06 7:49 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-06 7:55 ` [PATCH i-g-t v1] " B, Jeevan
2025-03-06 11:25 ` ✗ Xe.CI.Full: failure for " Patchwork
2025-03-10 3:14 ` Karthik B S
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=20250305103207.137714-1-vinod.govindapillai@intel.com \
--to=vinod.govindapillai@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jani.saarinen@intel.com \
--cc=santhosh.reddy.guddati@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