From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 85647] Random radeonsi crashes with mesa 10.3.x Date: Fri, 31 Oct 2014 02:31:56 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0348141989==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id DF8746E4C8 for ; Thu, 30 Oct 2014 19:31:55 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0348141989== Content-Type: multipart/alternative; boundary="1414722715.Af2AE70.19088"; charset="UTF-8" --1414722715.Af2AE70.19088 Date: Fri, 31 Oct 2014 02:31:55 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D85647 --- Comment #8 from Michel D=C3=A4nzer --- (In reply to Michel D=C3=A4nzer from comment #7) > That doesn't make it impossible, it just means you need patience. Take yo= ur > time, and make sure you test each commit for at least as long (preferably > longer, to account for variation) as it's ever taken for the problem to > occur before declaring it good. On the bright side, when the problem occu= rs > quickly, you know that commit is bad and can move on to the next one. On another bright side, when the problem doesn't occur for a long time, you= can enjoy the lack of complaints about it from your son. :) However, it's very important that you don't declare a commit good which would have exhibited t= he problem after more testing, otherwise the bisection will give the wrong res= ult. --=20 You are receiving this mail because: You are the assignee for the bug. --1414722715.Af2AE70.19088 Date: Fri, 31 Oct 2014 02:31:55 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Comment= # 8 on bug 85647<= /a> from Michel D=C3=A4nzer
(In reply to Michel D=C3=A4nzer from comment #7)
> That doesn't make it impossible, it just means y=
ou need patience. Take your
> time, and make sure you test each commit for at least as long (prefera=
bly
> longer, to account for variation) as it's ever taken for the problem to
> occur before declaring it good. On the bright side, when the problem o=
ccurs
> quickly, you know that commit is bad and can move on to the next one.<=
/span >

On another bright side, when the problem doesn't occur for a long time, you=
 can
enjoy the lack of complaints about it from your son. :) However, it's very
important that you don't declare a commit good which would have exhibited t=
he
problem after more testing, otherwise the bisection will give the wrong res=
ult.


You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1414722715.Af2AE70.19088-- --===============0348141989== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============0348141989==--