From: Gabriel Feceoru <gabriel.feceoru@intel.com>
To: Thomas Wood <thomas.wood@intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t] scripts: Add feature list file for piglit 'summary feature'
Date: Fri, 27 Nov 2015 17:04:31 +0200 [thread overview]
Message-ID: <565870FF.1070000@intel.com> (raw)
In-Reply-To: <CANkqdn2Ef0HXjsJDsDKdPg-VZ25inLJ+tKzJAuh_Q+-+fcc4Hg@mail.gmail.com>
On 26.11.2015 18:43, Thomas Wood wrote:
> On 25 November 2015 at 12:12, Gabriel Feceoru <gabriel.feceoru@intel.com> wrote:
>> This is a placeholder for the feature list file. Its content is just
>> an example.
>
> It would be useful if the example applied directly to intel-gpu-tools
> tests. Perhaps just a single feature to start with?
>
> Since this isn't a script as such, would it be better placed in the
> tests directory where the test list is generated?
Agree. Provided a 2nd version with these suggestions.
>
> It would probably be useful to integrate it with the run-tests.sh
> script as well.
Ok, but better in a separate patch. I think we need to get some
usability feedback on this one, to see what to add in run-tests.sh
(not sure if we stay with one file or use custom ones, as per need)
>
>
>> This needs to be filled in by feature owners with the feature name
>> and the corresponding tests regex.
>>
>> Please refer to this piglit commit for more info on this feature.
>>
>> commit f16d011db75b08ceae241e7370599146691340ab
>> Author: Feceoru, Gabriel <gabriel.feceoru@intel.com>
>> Date: Tue Nov 3 17:50:41 2015 +0200
>>
>> framework: Add support for feature readiness.
>>
>> Signed-off-by: Gabriel Feceoru <gabriel.feceoru@intel.com>
>> ---
>> scripts/feat_profile.json | 12 ++++++++++++
>> 1 file changed, 12 insertions(+)
>> create mode 100644 scripts/feat_profile.json
>>
>> diff --git a/scripts/feat_profile.json b/scripts/feat_profile.json
>> new file mode 100644
>> index 0000000..f3a21a3
>> --- /dev/null
>> +++ b/scripts/feat_profile.json
>> @@ -0,0 +1,12 @@
>> +{
>> + "glsl" : {
>> + "include_tests" : "glsl",
>> + "exclude_tests" : "",
>> + "target_rate" : 90
>> + },
>> + "arb" : {
>> + "include_tests" : "ARB_shader|deqp.arb shader",
>> + "exclude_tests" : "",
>> + "target_rate" : 10
>> + }
>> +}
>> --
>> 1.9.1
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-11-27 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 12:12 [PATCH i-g-t] scripts: Add feature list file for piglit 'summary feature' Gabriel Feceoru
2015-11-26 16:43 ` Thomas Wood
2015-11-27 15:04 ` Gabriel Feceoru [this message]
2015-11-27 14:56 ` [PATCH i-g-t v2] tests: " Gabriel Feceoru
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=565870FF.1070000@intel.com \
--to=gabriel.feceoru@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thomas.wood@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.