From: Ander Conselvan De Oliveira <conselvan2@gmail.com>
To: intel-gfx@lists.freedesktop.org
Subject: Adding custom bugzilla fields
Date: Fri, 26 Jun 2015 18:28:39 +0300 [thread overview]
Message-ID: <1435332519.3446.17.camel@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2718 bytes --]
Hi all,
I've been looking into creating custom fields in Bugzilla to help sort
our bugs in a more manageable way. I did some testing in a private
installation and came up with this proposal. In a nut shell, we would
add the following two fields:
i915 platform: list of platforms affected by a bug;
i915 features: list of features affected by a bug.
Both would be multiple selection fields. The accepted values would be
configured in the Bugzilla installation. The attached screenshots show
how this would look like in the bug view and bug list views.
My expectation is that using those fields we could have a clearer view
of which areas and/or platforms require more attention. For example, I
attached a screenshot of a sample report breaking down the bugs per
feature and platform. That report requires Bugzilla 5.0 (which hasn't
been released yet) since prior versions didn't support reports with
multiple selection fields. However, it is also possible to script a
similar report, as the attached python script does. The output looks
something like this:
Feature ALL ILK SNB BYT IVB HSW BDW BSW SKL
display - atomic 0 0 1 0 0 0 1 0 0
display - audio 0 0 0 0 0 0 0 0 0
display - DP 0 0 1 0 1 0 1 0 0
display - DP MST 0 0 0 0 0 0 0 0 0
display - DSI 0 0 0 0 0 0 0 0 0
display - eDP 0 0 0 0 0 0 0 0 0
display - fastboot 0 0 0 0 0 0 0 0 0
display - FBC 0 0 0 0 0 0 0 0 0
display - HDMI 0 0 0 0 0 0 0 0 0
display - IPS 0 0 0 0 0 0 0 0 0
display - LVDS 0 0 0 0 0 0 0 0 0
display - PSR 0 0 0 0 0 0 0 0 0
display - Other 0 0 0 0 0 0 0 0 0
GEM - execlists 0 0 0 0 0 0 0 0 0
GEM - PPGTT 0 0 0 0 0 0 0 0 0
GEM - Other 1 0 0 0 0 0 1 0 0
power - RC6 0 0 0 1 0 0 0 0 0
power - RCS 0 0 0 0 0 0 0 0 0
power - Other 0 0 0 0 0 0 0 0 0
So I would like to hear what other people think about this. Specially,
about what should be in the features field. The values can change
overtime, but would be good to have a good list from the start. The
values above are an incomplete list I threw together while looking at
different open bugs.
Thanks,
Ander
[-- Attachment #2: bug.png --]
[-- Type: image/png, Size: 72559 bytes --]
[-- Attachment #3: bug_list.png --]
[-- Type: image/png, Size: 66466 bytes --]
[-- Attachment #4: report.png --]
[-- Type: image/png, Size: 36688 bytes --]
[-- Attachment #5: features_vs_platform.py --]
[-- Type: text/x-python, Size: 1748 bytes --]
import bugzilla
import collections
bugzilla_url = "http://192.168.100.244/bugzilla/xmlrpc.cgi"
closed_states = ['RESOLVED', 'VERIFIED', 'CLOSED']
open_states = ["REOPENED", "NEEDINFO", "NEW", "ASSIGNED"]
def get_custom_fields_allowed_values(bz):
fields = ['cf_i915_platform', 'cf_i915_features']
r = bz._proxy.Bug.fields({'names': fields,
'include_fields': ['values']})
list_of_raw_values = [f['values'] for f in r['fields']]
values = [[v['name'] for v in f] for f in list_of_raw_values]
assert len(values) == len(fields)
return dict(zip(fields, values))
def get_drm_intel_bugs(bz):
query = bz.build_query(product="DRI", component="DRM/Intel",
status=open_states)
return bz.query(query)
def split_bugs_per_field(bz, bugs, field):
split = collections.OrderedDict()
allowed_values = get_custom_fields_allowed_values(bz)
for v in allowed_values[field]:
split[v] = []
for bug in bugs:
if field in bug.__dict__:
for value in bug.__dict__[field]:
split[value].append(bug)
return split
def intersect_lists(list1, list2):
return [v for v in list1 if v in list2]
def stringfy_list(l, spacing=5):
return ''.join([s.rjust(spacing) for s in map(str, l)])
if __name__ == "__main__":
bz = bugzilla.Bugzilla(url=bugzilla_url)
bugs = get_drm_intel_bugs(bz)
per_platform = split_bugs_per_field(bz, bugs, 'cf_i915_platform')
per_feature = split_bugs_per_field(bz, bugs, 'cf_i915_features')
print "Feature".ljust(20), stringfy_list(per_platform)
for feature in per_feature:
common_count = []
for platform in per_platform:
common = intersect_lists(per_feature[feature],
per_platform[platform])
common_count.append(len(common))
print feature.ljust(20), stringfy_list(common_count)
[-- Attachment #6: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2015-06-26 15:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 15:28 Ander Conselvan De Oliveira [this message]
2015-06-26 17:05 ` Adding custom bugzilla fields Daniel Vetter
2015-06-26 17:23 ` Chris Wilson
2015-06-26 17:34 ` Daniel Vetter
2015-06-29 7:42 ` Jani Nikula
2015-06-29 8:50 ` Ander Conselvan De Oliveira
2015-06-29 10:19 ` Ville Syrjälä
2015-06-29 10:26 ` Ville Syrjälä
2015-06-29 11:20 ` Ander Conselvan De Oliveira
2015-06-29 11:31 ` Ander Conselvan De Oliveira
2015-06-29 11:34 ` Chris Wilson
2015-06-29 11:46 ` Ander Conselvan De Oliveira
2015-06-29 11:47 ` Jani Nikula
2015-06-29 11:59 ` Ander Conselvan De Oliveira
2015-06-29 16:31 ` Daniel Vetter
2015-06-29 20:11 ` Chris Wilson
2015-06-30 10:05 ` Daniel Vetter
2015-06-30 10:07 ` Chris Wilson
2015-06-30 10:13 ` Chris Wilson
2015-06-30 12:14 ` Ander Conselvan De Oliveira
2015-08-21 8:41 ` Jani Nikula
2015-08-25 12:49 ` Daniel Vetter
2015-08-25 15:20 ` Jani Nikula
2015-08-28 6:50 ` Jani Nikula
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=1435332519.3446.17.camel@gmail.com \
--to=conselvan2@gmail.com \
--cc=intel-gfx@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 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.