One of the Leopard Debug slaves (apple-mac-pro-6) is still wedged
after the transition:
http://build.webkit.org/builders/Leopard%20Intel%20Debug%20%28Tests%29/builds/32142/steps/layout-test/logs/stdio
If someone could run killall httpd, or just restart the machine,
that'd be wonderful. :)
In
On Thu, Jul 7, 2011 at 10:46 AM, JOSE MANUEL CANTERA FONSECA j...@tid.eswrote:
Hi there,
** **
I have two technical questions concerning the Webkit Remote Debugging
Protocol.
** **
a/ What is the difference / relationship between this protocol and the v8
remote debugging
On 07/06/2011 07:24 PM, Eric Seidel wrote:
On Wed, Jul 6, 2011 at 10:18 AM, Xan Lopezx...@gnome.org wrote:
On Wed, Jul 6, 2011 at 6:29 PM, Eric Seidele...@webkit.org wrote:
NRWT uses both! It will read in all the port's Skipped files, covert
them to SKIP text_expectations, and add them to
On Jul 7, 2011, at 2:55 AM, Eric Seidel wrote:
One of the Leopard Debug slaves (apple-mac-pro-6) is still wedged
after the transition:
http://build.webkit.org/builders/Leopard%20Intel%20Debug%20%28Tests%29/builds/32142/steps/layout-test/logs/stdio
If someone could run killall httpd, or just
You need to check with Android port owners on whether they intend to enable
INSPECTOR in their builds and expose remote debugging capabilities.
I'm afraid we have no plans right now to enable this feature.
Steve
--
Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace
Hi,
This mailing list is for WebKit development not WebKit general
questions, use webkit-help for your next enquiries.
I am trying to use JavaScriptCore in my Android application.
First, understand that the Android bindings in WebKit have been
removed (that includes JSC), thus I would advise
I do not know the history as to why Chromium removed support for
test_expectations cascading.
Ideally we would have fewer test expectations, not more in the future. :)
On Thu, Jul 7, 2011 at 3:16 AM, Balazs Kelemen kbal...@webkit.org wrote:
On 07/06/2011 07:24 PM, Eric Seidel wrote:
On Wed,
One difference with the chromium port is that we try to use a single
test_expectations.txt that covers all platforms and OS versions (win xp,
vista, 7, mac leopard, snow leopard, linux 32, 64, GPU vs CPU, Debug vs
Release). The tokens to the left of the test name specify what
configuration the
On Thu, Jul 7, 2011 at 10:27 AM, Tony Chang t...@chromium.org wrote:
One difference with the chromium port is that we try to use a single
test_expectations.txt that covers all platforms and OS versions (win xp,
vista, 7, mac leopard, snow leopard, linux 32, 64, GPU vs CPU, Debug vs
Release).
On Jul 7, 2011, at 10:39 AM, Dirk Pranke wrote:
On Thu, Jul 7, 2011 at 10:27 AM, Tony Chang t...@chromium.org wrote:
One difference with the chromium port is that we try to use a single
test_expectations.txt that covers all platforms and OS versions (win xp,
vista, 7, mac leopard, snow
Hi all,
I've started adding a bunch of information on NRWT to the wiki. Some
of the pages are stubs at the moment, but the test_expectation page is
pretty complete. Other pages will be filled in over today and
tomorrow. Those of you who are also familiar with the functionality,
feel free to
11 matches
Mail list logo
