From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60302] piglit failures r600g radeon hd 6850
Date: Tue, 05 Feb 2013 09:09:19 +0000 [thread overview]
Message-ID: <bug-60302-502-OaXXGmwJAo@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-60302-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1063 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=60302
Michel Dänzer <michel@daenzer.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
--- Comment #1 from Michel Dänzer <michel@daenzer.net> ---
It's unrealistic to expect all piglit tests to pass, so I'm afraid this report
isn't useful.
Piglit is mostly useful in two ways:
* Regression testing, i.e. when a certain test used to pass but now fails, it's
good to try and get to the bottom of that and fix it.
* Specific tests reproducing failures which also affect real world apps. It's
usually easier to fix problems by investigating piglit tests than more complex
apps.
In both cases though, individual bugs should be reported for specific tests,
not a single one for all results as a whole.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2534 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-02-05 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 3:52 [Bug 60302] New: piglit failures r600g radeon hd 6850 bugzilla-daemon
2013-02-05 9:09 ` bugzilla-daemon [this message]
2013-02-05 12:12 ` [Bug 60302] " 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-60302-502-OaXXGmwJAo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox