<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [Regression, bisected] Tooltip corruption in Chrome" href="https://bugs.freedesktop.org/show_bug.cgi?id=90264#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [Regression, bisected] Tooltip corruption in Chrome" href="https://bugs.freedesktop.org/show_bug.cgi?id=90264">bug 90264</a> from <a class="email" href="mailto:freedesktop@mattwhitlock.name" title="Matt Whitlock <freedesktop@mattwhitlock.name>"> Matt Whitlock</a> <pre>(In reply to Furkan from <a href="show_bug.cgi?id=90264#c16">comment #16</a>) > What do those revision numbers represent? Are they binary builds? They don't > look like svn/git commits. They're Subversion revisions, which is what Chromium's bisect-builds.py script demands. bisect-builds.py also kicked out this ChangeLog URL: <a href="https://chromium.googlesource.com/chromium/src/+log/28ad5e6b1100a7f0d25a5e6741f7241a86cf61bd..1050ee48b1d8fe353bfc7df3b0ea4e5300260f5c">https://chromium.googlesource.com/chromium/src/+log/28ad5e6b1100a7f0d25a5e6741f7241a86cf61bd..1050ee48b1d8fe353bfc7df3b0ea4e5300260f5c</a> …but 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 when I upgraded Chromium from the former to the latter release, so those were my starting points for bisection.)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>