Given Maciej's and Adam's comments about these tests helping find
non-JS-engine-specific regressions, why not always run them?
On Wed, Aug 11, 2010 at 11:09 AM, Mads Sig Ager wrote:
> The V8 buildbots are running the sputnik tests and they do catch
> regressions for us. In the V8 repository we ha
Maybe a comment in the text_expectations file to point out where they are
run might be a good idea.
Avi
On Wed, Aug 11, 2010 at 2:27 PM, Dimitri Glazkov wrote:
> No apologies necessary! This was illuminating to me too, even though I
> _might have_ been the guy who put the "we probably don't want
No apologies necessary! This was illuminating to me too, even though I
_might have_ been the guy who put the "we probably don't want to run
these" comment in :P
:DG<
On Wed, Aug 11, 2010 at 11:19 AM, Eric Seidel wrote:
> Clearly I was misinformed. My apologies for using the webkit-dev list
> to
Clearly I was misinformed. My apologies for using the webkit-dev list
to track down this chromium-specific issue.
On Wed, Aug 11, 2010 at 11:09 AM, Mads Sig Ager wrote:
> The V8 buildbots are running the sputnik tests and they do catch
> regressions for us. In the V8 repository we have a list of
The V8 buildbots are running the sputnik tests and they do catch
regressions for us. In the V8 repository we have a list of V8 test
expectations for the sputnik tests.
http://build.chromium.org/buildbot/v8/waterfall
-- Mads
On Wed, Aug 11, 2010 at 7:32 PM, Ojan Vafai wrote:
> Just looking at th
Just looking at the history, it looks like when the tests were originally
checked in, they had no expected results. So someone on the chromium team
skipped them all. There's a comment in
http://trac.webkit.org/browser/trunk/LayoutTests/platform/chromium/test_expectations.txtthat
"we probably don't
If these tests are actually valuable, then maybe my question then
belongs: Why is Chromium no longer running these tests? (Assuming my
source is correct.)
-eric
On Wed, Aug 11, 2010 at 7:10 AM, Maciej Stachowiak wrote:
>
> On Aug 10, 2010, at 2:26 PM, Alexey Proskuryakov wrote:
>
>>
>> 10.08.20
On Aug 10, 2010, at 2:26 PM, Alexey Proskuryakov wrote:
>
> 10.08.2010, в 14:00, Adam Barth написал(а):
>
>> A better long-term fix might be to finish new-run-webkit-tests so we
>> can run the tests in parallel.
>
>
> One reason to move the tests to run-javascriptcore-tests is that people
>
Eric Seidel írta:
Chromium skips it (and if I remember correctly, they commissioned it?)
Why do we want to be running these 6000 tests and slowing down our
builds. I was talking with jamesr, and he seemed to think it adds
little value to run it every time? (It was supposedly written as more
of
10.08.2010, в 14:00, Adam Barth написал(а):
> A better long-term fix might be to finish new-run-webkit-tests so we
> can run the tests in parallel.
One reason to move the tests to run-javascriptcore-tests is that people working
on JS run these more often (sometimes not even building WebCore un
On Tue, Aug 10, 2010 at 12:16 PM, Alexey Proskuryakov wrote:
> 10.08.2010, в 11:51, Eric Seidel написал(а):
>> Why do we want to be running these 6000 tests and slowing down our
>> builds. I was talking with jamesr, and he seemed to think it adds
>> little value to run it every time? (It was sup
Nope, it's from Chromium:
http://blog.chromium.org/2009/06/launching-sputnik-into-orbit.html
http://blog.chromium.org/2010/03/does-your-browser-behave.html
Mihai
On Tue, Aug 10, 2010 at 1:30 PM, Dirk Pranke wrote:
> I thought Sputnik came from Microsoft?
>
> -- Dirk
>
> On Tue, Aug 10, 2010 at
I thought Sputnik came from Microsoft?
-- Dirk
On Tue, Aug 10, 2010 at 11:51 AM, Eric Seidel wrote:
> Chromium skips it (and if I remember correctly, they commissioned it?)
>
> Why do we want to be running these 6000 tests and slowing down our
> builds. I was talking with jamesr, and he seemed
10.08.2010, в 11:51, Eric Seidel написал(а):
> Why do we want to be running these 6000 tests and slowing down our
> builds. I was talking with jamesr, and he seemed to think it adds
> little value to run it every time? (It was supposedly written as more
> of a development tool for V8?) But may
Chromium skips it (and if I remember correctly, they commissioned it?)
Why do we want to be running these 6000 tests and slowing down our
builds. I was talking with jamesr, and he seemed to think it adds
little value to run it every time? (It was supposedly written as more
of a development tool
15 matches
Mail list logo
