- From: Tobie Langel <tobie@w3.org>
- Date: Tue, 17 Sep 2013 13:58:46 +0200
- To: James Graham <james@hoppipolla.co.uk>
- Cc: public-test-infra@w3.org
On Tuesday, September 17, 2013 at 10:55 AM, James Graham wrote: > On 16/09/13 18:37, James Graham wrote: > > > Good question. The easiest (hacky) way is to regenerate the local > > testharnessreport.js file for the testrun. However that only works if > > the multiplier (or equivalent) is fixed for the entire run. Supporting > > per-test overrides in this way would work in the absence of > > parallelisation, or with one test server per instance, but neither of > > those sound ideal. However the only way I can think of to pass in the > > timeout so that it is avaliable before any script has loaded is via a > > query parameter, which is something that I have traditionally resisted > > commandeering. > In general, this doesn't bother me as much as it bothers you; I see query params as the equivalent of params in a CLI. > Thinking about it, there are a couple of other things that would work. > But in fact I think the best option is to make it possible to disable > the timeout entirely in testharnessreport.js and let the external > harness deal with all cases where the timeout is reached. That sounds like an interesting and somewhat simpler option. --tobie
Received on Tuesday, 17 September 2013 11:58:49 UTC