Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Katarzyna Dec <katarzyna.dec@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v2 0/1] Add xe_mmap & xe_create tests to f-f
Date: Wed, 21 Jun 2023 12:47:36 +0000	[thread overview]
Message-ID: <20230621124737.1827262-1-katarzyna.dec@intel.com> (raw)

Adding new tests to BATs:

igt@xe_create@create-engines-noleak
igt@xe_create@create-engines-leak
igt@xe_create@create-massive-size
igt@xe_mmap@bad-flags
igt@xe_mmap@bad-extensions
igt@xe_mmap@bad-object

v2: Sort tests alphabetically

Katarzyna Dec (1):
  tests/intel-ci: Add xe_mmap & xe_create tests to f-f

 tests/intel-ci/xe-fast-feedback.testlist | 6 ++++++
 1 file changed, 6 insertions(+)

-- 
2.34.1

             reply	other threads:[~2023-06-21 12:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21 12:47 Katarzyna Dec [this message]
2023-06-21 12:47 ` [igt-dev] [PATCH i-g-t v2 1/1] tests/intel-ci: Add xe_mmap & xe_create tests to f-f Katarzyna Dec
2023-06-21 15:04 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2023-06-21 15:30 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-06-22  4:25 ` [igt-dev] ✗ Fi.CI.IGT: 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=20230621124737.1827262-1-katarzyna.dec@intel.com \
    --to=katarzyna.dec@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    /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