From: janga.rahul.kumar@intel.com
To: igt-dev@lists.freedesktop.org, ramadevi.gandi@intel.com,
janga.rahul.kumar@intel.com
Subject: [igt-dev] [PATCH i-g-t] tests/xe/xe_query: Add check for expected error
Date: Thu, 27 Apr 2023 17:41:58 +0530 [thread overview]
Message-ID: <20230427121158.3189360-1-janga.rahul.kumar@intel.com> (raw)
From: Janga Rahul Kumar <janga.rahul.kumar@intel.com>
For negavtive subtests, check for expected error value.
Signed-off-by: Janga Rahul Kumar <janga.rahul.kumar@intel.com>
---
tests/xe/xe_query.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/xe/xe_query.c b/tests/xe/xe_query.c
index 3f038225..ceb73c35 100644
--- a/tests/xe/xe_query.c
+++ b/tests/xe/xe_query.c
@@ -415,7 +415,7 @@ test_query_invalid_query(int fd)
.data = 0,
};
- igt_assert_eq(igt_ioctl(fd, DRM_IOCTL_XE_DEVICE_QUERY, &query), -1);
+ do_ioctl_err(fd, DRM_IOCTL_XE_DEVICE_QUERY, &query, EINVAL);
}
/**
@@ -432,7 +432,7 @@ test_query_invalid_size(int fd)
.data = 0,
};
- igt_assert_eq(igt_ioctl(fd, DRM_IOCTL_XE_DEVICE_QUERY, &query), -1);
+ do_ioctl_err(fd, DRM_IOCTL_XE_DEVICE_QUERY, &query, EINVAL);
}
igt_main
--
2.25.1
next reply other threads:[~2023-04-27 12:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 12:11 janga.rahul.kumar [this message]
2023-04-27 14:42 ` [igt-dev] ✗ GitLab.Pipeline: warning for tests/xe/xe_query: Add check for expected error Patchwork
2023-04-27 15:09 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-04-27 16:13 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/xe/xe_query: Add check for expected error (rev2) Patchwork
2023-04-27 20:39 ` [igt-dev] ✗ Fi.CI.IGT: failure for tests/xe/xe_query: Add check for expected error Patchwork
2023-04-27 22:04 ` [igt-dev] ✓ Fi.CI.IGT: success for tests/xe/xe_query: Add check for expected error (rev2) Patchwork
2023-04-28 11:04 ` [igt-dev] [PATCH i-g-t] tests/xe/xe_query: Add check for expected error Kamil Konieczny
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=20230427121158.3189360-1-janga.rahul.kumar@intel.com \
--to=janga.rahul.kumar@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=ramadevi.gandi@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