From: Lucas De Marchi <lucas.demarchi@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Subject: [PATCH i-g-t 1/2] build: Build xe tests by default
Date: Thu, 11 Jan 2024 13:33:57 -0800 [thread overview]
Message-ID: <20240111213358.1656641-1-lucas.demarchi@intel.com> (raw)
Swap the default value so xe tests are built by default. Once CI and
others are adapted, then the option can be removed.
Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
---
meson_options.txt | 9 ++-------
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/meson_options.txt b/meson_options.txt
index 12b5bb3c3..6a9493ea6 100644
--- a/meson_options.txt
+++ b/meson_options.txt
@@ -37,15 +37,10 @@ option('tests',
type : 'feature',
description : 'Build tests')
-# Currently, Xe uAPI is not stable: it may still change while the driver is
-# not merged upstream.
-# So, add an option to enable it, as distros shall not be shipping
-# binaries with Xe tests on it, as they will most certainly fail once
-# drivers get upstreamed.
option('xe_driver',
type : 'feature',
- value : 'disabled',
- description : 'Build tests for Xe driver (experimental)')
+ value : 'enabled',
+ description : 'Build tests for Xe driver')
option('libdrm_drivers',
type : 'array',
--
2.40.1
next reply other threads:[~2024-01-11 21:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 21:33 Lucas De Marchi [this message]
2024-01-11 21:33 ` [PATCH i-g-t 2/2] build: Remove xe_driver options Lucas De Marchi
2024-01-12 10:31 ` Kamil Konieczny
2024-01-15 7:14 ` Mauro Carvalho Chehab
2024-01-11 22:15 ` ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] build: Build xe tests by default Patchwork
2024-01-11 23:30 ` ✗ CI.xeBAT: failure " Patchwork
2024-01-15 13:23 ` Kamil Konieczny
2024-01-12 2:51 ` ✗ Fi.CI.IGT: " Patchwork
2024-01-15 13:39 ` Kamil Konieczny
2024-01-12 10:28 ` [PATCH i-g-t 1/2] " Kamil Konieczny
2024-01-15 7:15 ` Mauro Carvalho Chehab
2024-01-15 15:21 ` 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=20240111213358.1656641-1-lucas.demarchi@intel.com \
--to=lucas.demarchi@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