- From: Tony Gentilcore <tonyg@google.com>
- Date: Fri, 18 Mar 2011 15:14:20 -0700
- To: Philippe Le Hegaret <plh@w3.org>
- Cc: public-web-perf <public-web-perf@w3.org>
The tests are all updated[1] and passing once again. To reiterate the original concern expressed by Nic and myself: we need a process to ensure that when http://w3c-test.org/resources/testharness.js is updated, the tests that depend on it are run. Then the author of the change can either update any affected tests or at least notify the authors of affected tests. Where is the correct place to raise concerns about shared test infrastructure? -Tony [1] http://dvcs.w3.org/hg/webperf/rev/df4fe74dcee8 http://dvcs.w3.org/hg/webperf/rev/7fe5aea2f6a0 http://dvcs.w3.org/hg/webperf/rev/9cf6cfbe1346 http://dvcs.w3.org/hg/webperf/rev/73be2bf320e7 http://dvcs.w3.org/hg/webperf/rev/fb6cbccbb0cc
Received on Friday, 18 March 2011 22:15:21 UTC