W3C home > Mailing lists > Public > public-test-infra@w3.org > January to March 2017

Re: Storage clearing

From: Dirk Pranke <dpranke@chromium.org>
Date: Tue, 21 Mar 2017 10:28:19 -0700
Message-ID: <CAEoffTDmS2-H_t0L0j1nce+JOT9ec1P=EBY2xO4iF6bgxRNVTQ@mail.gmail.com>
To: Philip Jägenstedt <foolip@google.com>, James Graham <james@hoppipolla.co.uk>, public-test-infra <public-test-infra@w3.org>, Quinten Yearsley <qyearsley@chromium.org>, Jeff Carpenter <jeffcarp@chromium.org>
+qyearsley, jeffcarp ...

Yes, we could implement something one way or another in Blink pretty
easily, I'd think, but Quentin or Jeff could say for sure.

-- Dirk

On Tue, Mar 21, 2017 at 3:24 AM, Philip Jägenstedt <foolip@google.com>

> On Tue, Mar 21, 2017 at 6:49 PM James Graham <james@hoppipolla.co.uk>
> wrote:
>> On 21/03/17 05:52, Philip Jägenstedt wrote:
>> > Could that information be extracted out into the manifest? That seems
>> more
>> > straightforward than finding it and restarting.
>> Yes, sorry the scheme I had in mind would have the manifest generator
>> add this information to the manifest like we currently do for long
>> timeouts, so that wptrunner or similar would have access to it before
>> the test loaded.
> Dirk, do you know enough about how we launch tests to say if this would be
> workable in Blink? I'm guessing that we control the command line invocation
> for each test, can avoid batching together tests that need a clean slate,
> and run those tests using an empty profile?
Received on Tuesday, 21 March 2017 17:29:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:34:13 UTC