Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Petri Latvala <adrinael@adrinael.net>
To: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] meson: fix testplan building for old meson
Date: Tue, 16 May 2023 16:30:16 +0300	[thread overview]
Message-ID: <ZGOFaEP9/zBClGYL@adrinael.net> (raw)
In-Reply-To: <20230516084241.45226c0e@maurocar-mobl2>

On Tue, May 16, 2023 at 08:42:41AM +0200, Mauro Carvalho Chehab wrote:
> Hi Kamil,
> 
> On Mon, 15 May 2023 18:39:08 +0200
> Kamil Konieczny <kamil.konieczny@linux.intel.com> wrote:
> 
> > Old meson 0.47.2 do not support dictionary adding so fix
> > testplan building.
> > 
> > Cc: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
> > Signed-off-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> > ---
> >  docs/testplan/meson.build | 11 +++++++----
> >  1 file changed, 7 insertions(+), 4 deletions(-)
> > 
> > diff --git a/docs/testplan/meson.build b/docs/testplan/meson.build
> > index 2014f91b5..6454f2933 100644
> > --- a/docs/testplan/meson.build
> > +++ b/docs/testplan/meson.build
> > @@ -27,12 +27,15 @@ xe_test_dict = {
> >  		 'xe_tests': { 'input': xe_test_config, 'extra_args': check_testlist }
> >  	       }
> >  
> > -test_dict = {
> > +if build_xe
> > +	test_dict = {
> > +		'kms_tests': { 'input': kms_test_config, 'extra_args': [] },
> > +		'xe_tests': { 'input': xe_test_config, 'extra_args': check_testlist }
> > +	    }
> > +else
> > +	test_dict = {
> >  	      'kms_tests': { 'input': kms_test_config, 'extra_args': [] }
> >  	    }
> 
> This would mean that, for every new driver with documentation we'll
> need two changes. It would be even harder if we ever need to add options
> to control other driver builds.
> 
> Btw, I double-checked that, with meson, we can't update the directory
> with something like:
> 
> 	xe_tests = { 'input': xe_test_config, 'extra_args': check_testlist }
> 	test_dict['xe_tests'] = xe_tests
> 
> As this would generate this error:
> 
> 	../docs/testplan/meson.build:33:1: ERROR: Assignment target must be an id.
> 		test_dict['xe_tests'] = xe_tests
> 	 ^
> 
> According to [1]:
> 
> 	"All objects are immutable, you can not change the contents 
> 	 of them. You can only create new ones. 
> 	 (which is what += does behind the scenes)."
> 
> [1] https://github.com/mesonbuild/meson/issues/3931#issuecomment-407180830
> 
> On other words, with version < 0.48, we're stuck with data or code
> duplication.
> 
> So, IMO, we should:
> 
> 	1. Change the gitlab's "build:tests-fedora-oldest-meson" pipeline
> 	   to honor the minimal version from meson.build file, e. g.:
> 
> 		$ MESON_MIN_VERSION=$(perl -ne "print \$1 if (m/meson_version\s*:\s*'([^']+)/)" meson.build)
> 		$ echo $MESON_MIN_VERSION
> 		>=0.47.2
> 
> 	2. Update the minimal version to at least 0.48.
> 
> Yet, if there are strong reasons why keeping support for such old version,
> feel free to add my ack:
> 
> Acked-by: Mauro Carvalho Chehab <mchehab@kernel.org> # if we can't update meson_version to at least >= 0.48

The ideal fix for this is indeed bumping the minimum required version
to the oldest that's in Ubuntu LTS / Debian Stable / etc. However that
requires changing the docker image building in gitlab-CI to use the
new version and no one has had time to look into why any changes there
break all kinds of stuff. In other words: Not impossible, just not
possible quickly.


-- 
Petri Latvala


      reply	other threads:[~2023-05-16 13:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 16:39 [igt-dev] [PATCH i-g-t] meson: fix testplan building for old meson Kamil Konieczny
2023-05-15 17:32 ` Petri Latvala
2023-05-15 17:33 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-05-15 22:30 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-05-16  6:42 ` [igt-dev] [PATCH i-g-t] " Mauro Carvalho Chehab
2023-05-16 13:30   ` Petri Latvala [this message]

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=ZGOFaEP9/zBClGYL@adrinael.net \
    --to=adrinael@adrinael.net \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=mauro.chehab@linux.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