From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 90264] [Regression, bisected] Tooltip corruption in Chrome Date: Wed, 10 Jun 2015 21:12:21 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0230952157==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 720B672125 for ; Wed, 10 Jun 2015 14:12:21 -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 --===============0230952157== Content-Type: multipart/alternative; boundary="1433970741.a6CEeC3.24241"; charset="UTF-8" --1433970741.a6CEeC3.24241 Date: Wed, 10 Jun 2015 21:12:21 +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=3D90264 --- Comment #17 from Matt Whitlock --- (In reply to Furkan from comment #16) > What do those revision numbers represent? Are they binary builds? They do= n't > look like svn/git commits. They're Subversion revisions, which is what Chromium's bisect-builds.py scr= ipt demands. bisect-builds.py also kicked out this ChangeLog URL: https://chromium.googlesource.com/chromium/src/+log/28ad5e6b1100a7f0d25a5e6= 741f7241a86cf61bd..1050ee48b1d8fe353bfc7df3b0ea4e5300260f5c =E2=80=A6but it doesn't show any commits. I don't know why. The command line I used for bisecting was: $ ./bisect-builds.py -a linux64 --use-local-cache -g 323860 -b 330231 Revisions 323860 and 330231 correspond to releases 43.0.2357.73 and 44.0.2403.18, respectively. (The rendering problem appeared on my system wh= en I upgraded Chromium from the former to the latter release, so those were my starting points for bisection.) --=20 You are receiving this mail because: You are the assignee for the bug. --1433970741.a6CEeC3.24241 Date: Wed, 10 Jun 2015 21:12:21 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 17 on bug 90264<= /a> from Matt Whitlock 
(In reply to Furkan from comment #16)
> What do those revision numbers represent? Are th=
ey binary builds? They don't
> look like svn/git commits.

They're Subversion revisions, which is what Chromium's bisect-builds.py scr=
ipt
demands.

bisect-builds.py also kicked out this ChangeLog URL:

htt=
ps://chromium.googlesource.com/chromium/src/+log/28ad5e6b1100a7f0d25a5e6741=
f7241a86cf61bd..1050ee48b1d8fe353bfc7df3b0ea4e5300260f5c

=E2=80=A6but it doesn't show any commits. I don't know why.

The command line I used for bisecting was:

$ ./bisect-builds.py -a linux64 --use-local-cache -g 323860 -b 330231

Revisions 323860 and 330231 correspond to releases 43.0.2357.73 and
44.0.2403.18, respectively. (The rendering problem appeared on my system wh=
en I
upgraded Chromium from the former to the latter release, so those were my
starting points for bisection.)

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