From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v4 10/11] scripts/doc_to_xls.py: expand GPU excluded platform
Date: Fri, 8 Sep 2023 21:17:44 +0200 [thread overview]
Message-ID: <20230908211744.47d2efe6@maurocar-mobl2> (raw)
In-Reply-To: <20230908175614.bq75wyivv66sfyo6@kamilkon-desk.igk.intel.com>
On Fri, 8 Sep 2023 19:56:14 +0200
Kamil Konieczny <kamil.konieczny@linux.intel.com> wrote:
> > +expand_fields = {
> > + "GPU excluded platform": "blacklist "
> ------------------------------------------^
> Is it ok to have space there?
Yes. Basically, the string there is used as prefix as-is to the output.
So, for instance, if some test doesn't run on DG2, this will be
translated into:
blacklist DG2
This is more flexible than appending the space inside testlist class,
as it would allow things like:
"Foo": "foo"
will produce a XLS column:
foobar
if the documentation has:
Foo: bar
Regards,
Mauro
next prev parent reply other threads:[~2023-09-08 19:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 8:27 [igt-dev] [PATCH i-g-t v4 00/11] Xe: set Run type from testlist instead of defining it Mauro Carvalho Chehab
2023-09-08 8:27 ` [igt-dev] [PATCH i-g-t v4 01/11] test_list.py: add support for reading testlist regular expressions Mauro Carvalho Chehab
2023-09-08 17:47 ` Kamil Konieczny
2023-09-08 19:19 ` Mauro Carvalho Chehab
2023-09-11 8:51 ` Kamil Konieczny
2023-09-08 8:27 ` [igt-dev] [PATCH i-g-t v4 02/11] xe_test_config.json: add testlists and blacklists Mauro Carvalho Chehab
2023-09-08 8:27 ` [igt-dev] [PATCH i-g-t v4 03/11] kms_test_config.json: " Mauro Carvalho Chehab
2023-09-08 8:27 ` [igt-dev] [PATCH i-g-t v4 04/11] tests: Intel Xe: drop Run type field Mauro Carvalho Chehab
2023-09-08 10:00 ` Kamil Konieczny
2023-09-08 8:27 ` [igt-dev] [PATCH i-g-t v4 05/11] tests: Intel KMS: " Mauro Carvalho Chehab
2023-09-08 8:27 ` [igt-dev] [PATCH i-g-t v4 06/11] scripts/test_list.py: move "FULL" testlist to config file Mauro Carvalho Chehab
2023-09-08 17:48 ` Kamil Konieczny
2023-09-08 8:27 ` [igt-dev] [PATCH i-g-t v4 07/11] scripts/test_list.py: don't be greedy while matching data from testlists Mauro Carvalho Chehab
2023-09-08 17:49 ` Kamil Konieczny
2023-09-08 8:27 ` [igt-dev] [PATCH i-g-t v4 08/11] scripts/test_list.py: fix gen_testlist logic Mauro Carvalho Chehab
2023-09-08 17:51 ` Kamil Konieczny
2023-09-08 8:27 ` [igt-dev] [PATCH i-g-t v4 09/11] scripts/test_list.py: add support for expanding fields on spreadsheet Mauro Carvalho Chehab
2023-09-08 17:53 ` Kamil Konieczny
2023-09-08 8:27 ` [igt-dev] [PATCH i-g-t v4 10/11] scripts/doc_to_xls.py: expand GPU excluded platform Mauro Carvalho Chehab
2023-09-08 17:56 ` Kamil Konieczny
2023-09-08 19:17 ` Mauro Carvalho Chehab [this message]
2023-09-11 9:04 ` Kamil Konieczny
2023-09-08 8:27 ` [igt-dev] [PATCH i-g-t v4 11/11] scripts/doc_to_xls.py: improve XLS output format Mauro Carvalho Chehab
2023-09-08 17:57 ` Kamil Konieczny
2023-09-08 9:25 ` [igt-dev] ✗ CI.xeBAT: failure for Xe: set Run type from testlist instead of defining it Patchwork
2023-09-08 9:28 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-09-08 15:05 ` [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=20230908211744.47d2efe6@maurocar-mobl2 \
--to=mauro.chehab@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@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