On Wed, Mar 2, 2011 at 7:36 AM, Ryosuke Niwa rn...@webkit.org wrote:
I'm specifically asking for the convenient time for Chromium, GTK, Qt, and
Windows ports since they have test bots running on build.webkit.org.
For Qt, most people are in CET timezone. It would be nice if you wait for
the
En 02/03/11 10:53, Benjamin escribiu:
On Wed, Mar 2, 2011 at 7:36 AM, Ryosuke Niwa rn...@webkit.org
mailto:rn...@webkit.org wrote:
I'm specifically asking for the convenient time for Chromium, GTK,
Qt, and Windows ports since they have test bots running on
build.webkit.org
Since Windows 7 is green now, can I try to land it 2 hours from now?
http://www.timeanddate.com/worldclock/meetingdetails.html?year=2011month=3day=2hour=11min=0sec=0p1=248p2=195p3=179p4=224
- Ryosuke
On Wed, Mar 2, 2011 at 7:24 PM, Sergio Villar Senin svil...@igalia.comwrote:
En 02/03/11
I'm in CET, but I'm flexible. I will have time between
08:00-02:00 in CET, 17:00-11:00 in PST and 0:00-18:00 in JST.
Please tell me the exact time and I will be online at the time.
Ossy
Ryosuke Niwa írta:
*When is the best time to land a massive patch that requires rebaselines
of about 165
Ooops, I miscalculated. :) (All times are in 24h format.)
The following interval is good for me everyday.
08:00 - 02:00 in CET
23:00 - 17:00 in PST
16:00 - 10:00 in JST
Osztrogonac Csaba írta:
I'm in CET, but I'm flexible. I will have time between
08:00-02:00 in CET, 17:00-11:00 in PST and
On Mar 2, 2011, at 2:33 AM, Ryosuke Niwa wrote:
I just realized that there's a new field labelled Alias on
https://bugs.webkit.org/enter_bug.cgi?product=WebKit
Why is this field added and what should I put in this field?
The Alias field allows a bug to be referred to by something other
Ah, ok. Thanks for the clarification.
- Ryosuke
On Wed, Mar 2, 2011 at 11:23 PM, Adam Roben aro...@apple.com wrote:
On Mar 2, 2011, at 2:33 AM, Ryosuke Niwa wrote:
I just realized that there's a new field labelled Alias on
https://bugs.webkit.org/enter_bug.cgi?product=WebKit
Why is this
Hi all-
All of Apple's Mac and Windows test bots should now be uploading crash logs to
build.webkit.org [1]. The crash logs are linked to from results.html (e.g.,
http://build.webkit.org/results/Windows%20XP%20Debug%20(Tests)/r80125%20(25890)/results.html).
If you see a crash on one of Apple's
The patch has been landed successfully. Thanks all for your help.
- Ryosuke
On Wed, Mar 2, 2011 at 3:21 PM, Ryosuke Niwa rn...@webkit.org wrote:
Hi,
*When is the best time to land a massive patch that requires rebaselines
of about 165 tests?*
I'm going to land my
Hi all-
I'd like to understand better what the criteria are for a builder to become a
core builder.
We've been putting lot of effort into keeping the Windows testers green lately
(especially the Windows 7 Release (Tests) builder), and it seems like it would
be good for them to eventually join
I'm somewhat sad at having helped create this concept of Core, since
it's generated much confusion. It was/is intended more as a way to
get non-stable buildbots off the main page, and away from distracting
developers and bots.
IMO the core list should be *descriptive* rather than
Does this require special configuration on the bots, or should
run-webkit-tests be copying crash logs into layout-test-results for
all Snow Leopard machines?
I ask, because the EWS and commit-queue snow leopard machines do not
seem to be copying crash logs into layout-test-results like I would
On Mar 2, 2011, at 1:41 PM, Eric Seidel wrote:
Does this require special configuration on the bots, or should
run-webkit-tests be copying crash logs into layout-test-results for
all Snow Leopard machines?
run-webkit-tests should be copying crash logs into layout-test-results for all
Snow
On Mar 2, 2011, at 1:38 PM, Eric Seidel wrote:
So if you believe the windows bots are regularly green, you should
make them Core.
Well, they are regularly green except for the cases I mentioned. The biggest
problem is people making changes that cause tests to fail on Windows and not
noticing
On Wed, Mar 2, 2011 at 7:38 PM, Eric Seidel e...@webkit.org wrote:
IMO the core list should be *descriptive* rather than *prescriptive*.
If a bot is regularly green, it should be core. If its not, it should
be non-core. We should not remove bots we don't like, or add bots
we hope to stay
I've used fiddler2 in some special cases, and it's really come in handy
with experimenting on live sites.
Fiddler2 just acts as a simple http proxy, to hijack requests to
particular resources and redirect them to another location and/or local
file.
The breakpoints mechanism in WebKit
On Mar 2, 2011, at 1:41 PM, Eric Seidel wrote:
the EWS and commit-queue snow leopard machines do not
seem to be copying crash logs into layout-test-results like I would
expect:
https://bugs.webkit.org/show_bug.cgi?id=51138
(each of those zips are made from /tmp/layout-test-results after the
17 matches
Mail list logo
