From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107448] [r600g] 2 of 5 piglit sanity tests fail (PCIe, ppc64, mesa-18.1.5)
Date: Fri, 19 Oct 2018 20:05:54 +0000 [thread overview]
Message-ID: <bug-107448-502-5DiGiwyTuJ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107448-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 327 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107448
--- Comment #6 from erhard_f@mailbox.org ---
Meanwhile, on another machine (Talos II + Radeon HD 6450), another mesa
(18.2.2) and rebuilt piglit from git-master. But same test-failures here.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1126 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-10-19 20:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 18:36 [Bug 107448] [r600g] 2 of 5 piglit sanity tests fail (PCIe, ppc64, mesa-18.1.5) bugzilla-daemon
2018-08-01 18:37 ` bugzilla-daemon
2018-08-01 18:51 ` bugzilla-daemon
2018-08-01 18:56 ` bugzilla-daemon
2018-08-01 19:01 ` bugzilla-daemon
2018-08-03 12:50 ` bugzilla-daemon
2018-08-03 13:05 ` bugzilla-daemon
2018-10-19 20:05 ` bugzilla-daemon [this message]
2018-10-19 20:06 ` [Bug 107448] [r600g] 2 of 5 piglit sanity tests fail (PCIe, ppc64, mesa-18.2.2) bugzilla-daemon
2019-03-10 17:11 ` bugzilla-daemon
2019-03-10 17:23 ` bugzilla-daemon
2019-03-10 17:27 ` [Bug 107448] [r600g] 5 of 30 piglit sanity tests fail (PCIe, ppc64, mesa-18.3.4) bugzilla-daemon
2019-03-10 17:36 ` bugzilla-daemon
2019-09-18 19:26 ` 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-107448-502-5DiGiwyTuJ@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