Re: [webkit-dev] commit-queue usernames?

Just as a warning: changing commits after the fact can cause git.webkit.org to get out of sync (it can mirror before the username change goes through). I don't think that's a reason to not make a change like this, but it would be good to figure out how to handle this before you make it live. On W

[webkit-dev] Compile failures on Leopard build bot

Hi! One of 2 slaves (apple-xserve-1 <../../../buildslaves/apple-xserve-1>) on that bot fails Release compile: http://build.webkit.org/builders/Leopard%20Intel%20Release%20(Build)/builds/12151 It seems like because of incremental build after http://trac.webkit.org/changeset/54411, it now has DOMBl

Re: [webkit-dev] commit-queue usernames?

Woh. Looks like this is the real deal: https://svn.apache.org/repos/asf/subversion/trunk/contrib/server-side/svn-tweak-author.py I'll work with Bill and see if we can wire up some magic. :) -eric On Wed, Mar 17, 2010 at 4:40 PM, Eric Seidel wrote: > http://home.introweb.nl/d/dodger/svnauthor.h

[webkit-dev] commit-queue usernames?

http://home.introweb.nl/d/dodger/svnauthor.html Could it be? Anyone know if that could actually work for changing authorship after-the-fact? -eric ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webk

Re: [webkit-dev] Web developer documentation - working with Mozilla

On Mar 17, 2010, at 8:55 AM, henry.haveri...@nokia.com wrote: Hi everyone, I'm working for the Qt port of WebKit, and we're currently considering different ways of creating web developer documentation for our users. We don't currently have any documentation for web developers We'd like

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

On Mar 17, 2010, at 12:14 PM, Kenneth Russell wrote: I think what should be done is to get the tree green by skipping these flaky tests; file high-priority bugs against the test authors to fix the flakiness; and then figure out a way the commit queue can be used for the vast majority of

Re: [webkit-dev] A mechanism for detecting red bots (was Re: Yet another email about a broken tree)

On Mar 17, 2010, at 9:10 AM, Adam Barth wrote: On Wed, Mar 17, 2010 at 2:16 AM, Maciej Stachowiak wrote: That being said, the mechanism I'd really like to see first is better notification of when the bot goes red (I suspect a number of people involved in today's redness didn't notice right

Re: [webkit-dev] Web developer documentation - working with Mozilla

On Wed, Mar 17, 2010 at 8:55 AM, wrote: > We don't currently have any documentation for web developers We'd like to > start with best practice articles and tutorials for some > HTML5 and CSS3 features but later extend to the basics and general > reference guides too. This sounds like the missi

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

On 17.03.2010, at 12:14, Kenneth Russell wrote: websocket/tests/frame-lengths.html is one. This tests needs to be broken into several pieces to reliably pass in the time allowed. Or perhaps timeouts in run-webkit-tests and DRT should be increased. I'm not sure which is better - the curren

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

On Wed, Mar 17, 2010 at 2:52 AM, Maciej Stachowiak wrote: > > On Mar 17, 2010, at 2:31 AM, Kenneth Russell wrote: > >> >> Our best current plan is more widespread testing. We will file a Radar >> bug as soon as we have more information about the nature of the >> failure -- by virtue of working aro

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

On 17.03.2010, at 0:45, Xan Lopez wrote: Manual investigation confirms 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? FWIW this patch seems to only add

Re: [webkit-dev] Frustrations with WebKit Font Representation

I'd say for our configuration that uses wince/cairo and rendering with freetype that this is a welcome move as we've been working with this font configuration between cairo and windows CE and copying the gtk code over manually for now to get it working. I haven't yet integrated this change into ou

Re: [webkit-dev] Frustrations with WebKit Font Representation

Hi Gustavo, On Wed, Mar 17, 2010 at 7:22 AM, Gustavo Noronha Silva wrote: > While I agree with the rest of your email, I failed to understand the > actual problem this caused. Is it because the include path for > platform/graphics/cairo is coming before the one you were using, and > then picking

[webkit-dev] A mechanism for detecting red bots (was Re: Yet another email about a broken tree)

On Wed, Mar 17, 2010 at 2:16 AM, Maciej Stachowiak wrote: > That being said, the mechanism I'd really like to see first is better > notification of when the bot goes red (I suspect a number of people involved > in today's redness didn't notice right away because there is no active > notification s

[webkit-dev] Web developer documentation - working with Mozilla

Hi everyone, I'm working for the Qt port of WebKit, and we're currently considering different ways of creating web developer documentation for our users. We don't currently have any documentation for web developers We'd like to start with best practice articles and tutorials for some HTML5 a

Re: [webkit-dev] Frustrations with WebKit Font Representation

On Tue, 2010-03-16 at 15:49 -0700, Brent Fulgham wrote: > Recently, an update that attempted to share more Cairo-related font > code was added to the WebKit repository > (http://trac.webkit.org/changeset/55510). While this was no doubt of > great benefit to the Gtk-based ports, it had the unintend

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

On Mar 17, 2010, at 2:31 AM, Kenneth Russell wrote: Our best current plan is more widespread testing. We will file a Radar bug as soon as we have more information about the nature of the failure -- by virtue of working around the bugs. If we knew the precise hardware configuration of the bots,

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

On Wed, Mar 17, 2010 at 2:16 AM, Maciej Stachowiak wrote: > > On Mar 17, 2010, at 1:49 AM, Kenneth Russell wrote: > >> On Wed, Mar 17, 2010 at 12:44 AM, Maciej Stachowiak wrote: >>> >>> On Mar 17, 2010, at 12:02 AM, Adam Barth wrote: >>> Manual investigation seems to implicate

Re: [webkit-dev] ie test center

On Mar 17, 2010, at 1:55 AM, Dirk Schulze wrote: Hi, Microsoft announced a new test suite, the "Internet Explorer testing center" together with the first preview of the upcoming ie9. http://samples.msdn.microsoft.com/ietestcenter/ In one table the "current" releases of the major browsers are

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

On Mar 17, 2010, at 1:49 AM, Kenneth Russell wrote: On Wed, Mar 17, 2010 at 12:44 AM, Maciej Stachowiak wrote: On Mar 17, 2010, at 12:02 AM, Adam Barth wrote: Manual investigation seems to implicate for at least some of the brokenness in SnowLeopa

[webkit-dev] ie test center

Hi, Microsoft announced a new test suite, the "Internet Explorer testing center" together with the first preview of the upcoming ie9. http://samples.msdn.microsoft.com/ietestcenter/ In one table the "current" releases of the major browsers are compared to ie9. Safari and Chrome do fail on more th

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

On Wed, Mar 17, 2010 at 12:44 AM, Maciej Stachowiak wrote: > > On Mar 17, 2010, at 12:02 AM, Adam Barth wrote: > >> >> Manual investigation seems to implicate >> for at least some of the >> brokenness in SnowLeopard Intel Release (Tests).  There's a patch i

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

On Wed, Mar 17, 2010 at 9:02 AM, Adam Barth wrote: > Manual investigation confirms > 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? FWIW this patch seems to on

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

On Mar 17, 2010, at 12:02 AM, Adam Barth wrote: Manual investigation seems to implicate for at least some of the brokenness in SnowLeopard Intel Release (Tests). There's a patch in that claims to fix thin

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

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 (Tes