From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111630] Generate a list of tags for the machine that runs the testsuite
Date: Tue, 10 Sep 2019 10:28:14 +0000 [thread overview]
Message-ID: <bug-111630-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1237 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111630
Bug ID: 111630
Summary: Generate a list of tags for the machine that runs the
testsuite
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: not set
Priority: not set
Component: IGT
Assignee: dri-devel@lists.freedesktop.org
Reporter: martin.peres@free.fr
Bug filing is done based on machine tags. They can be indicating a platform
(TGL, SKL, ...), or a configuration (HDMI, PSR, CHAMELIUM, ...).
This tagging is currently done manually, but it often is not in sync with the
current platform state, which makes bug filing difficult and leads to random
noise in CI until the proper tag is set.
Since we would like individual developers and CI machines to have a consistent
way of creating these tags (so as individual developers can filter out the
known issues from their run locally), having an IGT test/utility to generate
these tags would be ideal.
I'll let Arek explain how it could be done :)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2527 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-09-10 10:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 10:28 bugzilla-daemon [this message]
2019-09-10 10:52 ` [Bug 111630] Generate a list of tags for the machine that runs the testsuite bugzilla-daemon
2019-11-12 7:41 ` bugzilla-daemon
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=bug-111630-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@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.