On Mon, 11 Jul 2011 21:30:44 -0700, Brent Fulgham
wrote:
>> Is the WinCE port still active?
>
> I don't know about your other questions, but Patrick Gansterer (paroga)
> maintains the WinCE port. I believe it is active.
Correct, I still maintain the WinCE port and provide the buildbot for it.
Hi Eric,
On Jul 11, 2011, at 11:46 AM, Eric Seidel wrote:
> There is code in old-run-webkit-tests attempting to support "msys"
> configurations. (Which appears to be used by the WinCE port?)
>
> Is this an active configuration? Or can we remove "msys" support when
> transitioning to new-run-we
As part of fixing https://bugs.webkit.org/show_bug.cgi?id=64086 I
found that only the CYGWIN port still uses Apache 1.3. However, it
has its own special httpd.conf file to do so.
Now that Tiger is removed (and all known linux ports have moved to
Apache 2), LayoutTests/httpd/conf/http.conf no long
On Mon, Jul 11, 2011 at 1:34 PM, Leandro Pereira wrote:
> I like this idea, in general. However, since some ports (GTK+ and EFL,
> for instance) shares the same backends (Cairo, FontConfig, Pango,
> etc.), pixel tests are often the same.
It's been my experience that pixel results for Cairo ports
On Sun, Jul 10, 2011 at 2:52 PM, Adam Barth wrote:
> These changes might increase the number of image baselines we store in
> the tree for "chromium-mac"-derived ports (because there will be fewer
> redundant fallback paths), but I expect that cost to be relatively
> small because essentially ever
On Mon, Jul 11, 2011 at 1:02 PM, Gustavo Noronha Silva wrote:
>
> That seems to not be the case for gtk+ 32 bits release. When a single
> test fails or crashes it is showing all tests that have no expected
> results as failures, apparently, and when there are only flaky tests
> reported the bot is
On Wed, 2011-07-06 at 09:11 -0700, Ryosuke Niwa wrote:
> For flaky tests, you can add
> BUG# :
> http/tests/misc/favicon-loads-with-icon-loading-override.html = TEXT
> PASS
> in mac or mac-leopard test_expectations.txt
>
>
> Although flaky tests only make the bots orange.
That seems to not
On Mon, Jul 11, 2011 at 10:46 AM, Adam Barth wrote:
>
> There are two main benefits:
>
> 1) A tree is much easier to understand than a rats nest of interwoven
> fallback paths.
I find it impossible to know what the fallback path is. Even with Adam's
graph, it is hard to figure it out as Mark dem
On Mon, Jul 11, 2011 at 10:46 AM, Adam Barth wrote:
> On Mon, Jul 11, 2011 at 12:30 AM, Maciej Stachowiak wrote:
>> On Jul 10, 2011, at 12:11 PM, Adam Barth wrote:
>>> On Sun, Jul 10, 2011 at 12:01 PM, James Robinson wrote:
On Jul 10, 2011 10:53 AM, "Adam Barth" wrote:
> Hi webkit-dev,
There is code in old-run-webkit-tests attempting to support "msys"
configurations. (Which appears to be used by the WinCE port?)
Is this an active configuration? Or can we remove "msys" support when
transitioning to new-run-webkit-tests.
Is the WinCE port still active?
-eric
__
On Mon, Jul 11, 2011 at 12:30 AM, Maciej Stachowiak wrote:
> On Jul 10, 2011, at 12:11 PM, Adam Barth wrote:
>> On Sun, Jul 10, 2011 at 12:01 PM, James Robinson wrote:
>>> On Jul 10, 2011 10:53 AM, "Adam Barth" wrote:
Hi webkit-dev,
In trying to understand how our LayoutTest resul
On Jul 10, 2011, at 3:55 PM, Adam Barth wrote:
> Because the LayoutTest fallback graph is a mess, hence this email thread. :)
>
> More proximately, because when the "chromium-mac-leopard" (for
> example) fallback path flows through "mac-leopard", it flows to
> "mac-snowleopard" alongside the fa
On Jul 10, 2011, at 12:11 PM, Adam Barth wrote:
> On Sun, Jul 10, 2011 at 12:01 PM, James Robinson wrote:
>> On Jul 10, 2011 10:53 AM, "Adam Barth" wrote:
>>> Hi webkit-dev,
>>>
>>> In trying to understand how our LayoutTest results system works, I've
>>> created a digram of the fallback graph
13 matches
Mail list logo
