[webkit-dev] Yet another email about a broken tree

[Adam Barth]

It seems that some of the build bots have now been broken longer than
we have records on build.webkit.org:

$ ./WebKitTools/Scripts/webkit-patch what-broke
Tiger Intel Release               : FAIL (blame-list: sometime before 56055?)
Leopard Intel Release (Build)     : ok
Leopard Intel Release (Tests)     : ok
Leopard Intel Debug (Build)       : ok
Leopard Intel Debug (Tests)       : ok
SnowLeopard Intel Release (Build) : ok
SnowLeopard Intel Release (Tests) : FAIL (blame-list: sometime before 56064?)
SnowLeopard Intel Leaks           : FAIL (blame-list: sometime before 56057?)
Windows Release (Build)           : ok
Windows Release (Tests)           : FAIL (blame-list: sometime before 56060?)
Windows Debug (Build)             : ok
Windows Debug (Tests)             : FAIL (blame-list: sometime before 56062?)
GTK Linux 32-bit Release          : FAIL (blame-list: [56079])
GTK Linux 32-bit Debug            : FAIL (blame-list: sometime before 56052?)
GTK Linux 64-bit Debug            : FAIL (blame-list: sometime before 56054?)
GTK Linux 64-bit Release          : FAIL (blame-list: [56070])
Qt Linux Release                  : FAIL (blame-list: [56079])
Chromium Win Release              : ok
Chromium Mac Release              : ok
Chromium Linux Release            : ok

Do we have a plan for fixing the tree?

webkit-patch what-broke is an experimental tool for diagnosing redness
in the tree.  It's blame-lists might not be entirely accurate yet.

Manual investigation seems to implicate
<http://trac.webkit.org/changeset/56044> for at least some of the
brokenness in Windows Debug (Tests).  I've rolled out the offending
patch.

Manual investigation seems to implicate
<http://trac.webkit.org/changeset/56074> for at least some of the
brokenness in SnowLeopard Intel Release (Tests).  There's a patch in
<https://bugs.webkit.org/show_bug.cgi?id=36194> that claims to fix
things, but the brokenness has been polluting the tree for 12 hours.
Is there some reason we didn't roll out the offending patch?

Manual investigation confirms <http://trac.webkit.org/changeset/56079>
broke GTK Linux 32-bit Release, GTK Linux 64-bit Release, and Qt Linux
Release.  Is there some reason we didn't roll out the offending patch?

Adam