web-platform-tests sync status, as of September 29

4 views
Skip to first unread message

Quinten Yearsley

unread,
Sep 29, 2017, 6:03:46 PM9/29/17
to blink-inf...@chromium.org, ecosystem-infra
Changes in the past couple weeks:

Import:
Export:
Thanks Robert :-)

Other updates:
  • BlinkOn8 happened last week, and there seems to be continued general interest in wpt (as evidenced by number of people attending the talk about wpt).
  • In Q4, the ecosystem infra OKRs around import and export will be about latency: In general, there is a goal is that import latency should be less than 12 hours, and export should be in less than 1 hour.
  • Also, I don't plan to continue sending out updates in this format in Q4, although there are still exciting changes in the future. Some recent changes can still be seen by checking out recent code changes in the importer/exporter code (webkitpy/w3c/).

Philip Jägenstedt

unread,
Sep 30, 2017, 4:58:52 AM9/30/17
to Quinten Yearsley, blink-inf...@chromium.org, ecosystem-infra
On Sat, Sep 30, 2017 at 12:03 AM 'Quinten Yearsley' via ecosystem-infra <ecosyst...@chromium.org> wrote:
Changes in the past couple weeks:

Import:
Export:
Awesome, does that mean that the lint is also updated? I've been secretly worrying about what will happen if it gets out of sync, so some way of keeping wpt tools more regularly in sync would be good.

On a related note, is testharness.js in sync now as well?

Thanks Robert :-)

Other updates:
  • BlinkOn8 happened last week, and there seems to be continued general interest in wpt (as evidenced by number of people attending the talk about wpt).
  • In Q4, the ecosystem infra OKRs around import and export will be about latency: In general, there is a goal is that import latency should be less than 12 hours, and export should be in less than 1 hour.
  • Also, I don't plan to continue sending out updates in this format in Q4, although there are still exciting changes in the future. Some recent changes can still be seen by checking out recent code changes in the importer/exporter code (webkitpy/w3c/).

--
You received this message because you are subscribed to the Google Groups "ecosystem-infra" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ecosystem-inf...@chromium.org.
To post to this group, send email to ecosyst...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/ecosystem-infra/CAFp4ESnohTnnY87b8317ch1qfF%2Bi8i%2Bg_v6GZLE0A8kw8uwSHQ%40mail.gmail.com.

Robert Ma

unread,
Sep 30, 2017, 8:11:14 AM9/30/17
to Philip Jägenstedt, Quinten Yearsley, blink-inf...@chromium.org, ecosystem-infra
Thank you, Quinten!

Philip, lint is now up-to-date. However, testharness is not. I know our testharnessreport is home baked and cannot be synced. What about testharness?

On Sep 30, 2017 04:58, "'Philip Jägenstedt' via blink-infra" <blink...@chromium.org> wrote:
On Sat, Sep 30, 2017 at 12:03 AM 'Quinten Yearsley' via ecosystem-infra <ecosyst...@chromium.org> wrote:
Changes in the past couple weeks:

Import:
Export:
Awesome, does that mean that the lint is also updated? I've been secretly worrying about what will happen if it gets out of sync, so some way of keeping wpt tools more regularly in sync would be good.

On a related note, is testharness.js in sync now as well?

Thanks Robert :-)

Other updates:
  • BlinkOn8 happened last week, and there seems to be continued general interest in wpt (as evidenced by number of people attending the talk about wpt).
  • In Q4, the ecosystem infra OKRs around import and export will be about latency: In general, there is a goal is that import latency should be less than 12 hours, and export should be in less than 1 hour.
  • Also, I don't plan to continue sending out updates in this format in Q4, although there are still exciting changes in the future. Some recent changes can still be seen by checking out recent code changes in the importer/exporter code (webkitpy/w3c/).

--
You received this message because you are subscribed to the Google Groups "ecosystem-infra" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ecosystem-infra+unsubscribe@chromium.org.

--
You received this message because you are subscribed to the Google Groups "blink-infra" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-infra+unsubscribe@chromium.org.
To post to this group, send email to blink...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-infra/CAARdPYfaw0v5mARQYQb8ecJB0TMD1cz%2B1T23v%2BQJfttqVpjUTg%40mail.gmail.com.

Philip Jägenstedt

unread,
Sep 30, 2017, 8:44:51 AM9/30/17
to Robert Ma, Quinten Yearsley, blink-inf...@chromium.org, ecosystem-infra
testharness.js ought to be synced regularly, Quinten filed https://bugs.chromium.org/p/chromium/issues/detail?id=685854 some time ago about that.

On Sat, Sep 30, 2017 at 2:11 PM Robert Ma <robe...@google.com> wrote:
Thank you, Quinten!

Philip, lint is now up-to-date. However, testharness is not. I know our testharnessreport is home baked and cannot be synced. What about testharness?

On Sep 30, 2017 04:58, "'Philip Jägenstedt' via blink-infra" <blink...@chromium.org> wrote:
On Sat, Sep 30, 2017 at 12:03 AM 'Quinten Yearsley' via ecosystem-infra <ecosyst...@chromium.org> wrote:
Changes in the past couple weeks:

Import:
Export:
Awesome, does that mean that the lint is also updated? I've been secretly worrying about what will happen if it gets out of sync, so some way of keeping wpt tools more regularly in sync would be good.

On a related note, is testharness.js in sync now as well?

Thanks Robert :-)

Other updates:
  • BlinkOn8 happened last week, and there seems to be continued general interest in wpt (as evidenced by number of people attending the talk about wpt).
  • In Q4, the ecosystem infra OKRs around import and export will be about latency: In general, there is a goal is that import latency should be less than 12 hours, and export should be in less than 1 hour.
  • Also, I don't plan to continue sending out updates in this format in Q4, although there are still exciting changes in the future. Some recent changes can still be seen by checking out recent code changes in the importer/exporter code (webkitpy/w3c/).

--
You received this message because you are subscribed to the Google Groups "ecosystem-infra" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ecosystem-inf...@chromium.org.

--
You received this message because you are subscribed to the Google Groups "blink-infra" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-infra...@chromium.org.

Quinten Yearsley

unread,
Oct 2, 2017, 12:02:35 PM10/2/17
to Philip Jägenstedt, Robert Ma, blink-inf...@chromium.org, ecosystem-infra
Good point: testharness.js is out of date, and that's important because differences in our testharness.js and the upstream version make it harder for people to upstream tests.

(Updated the bug.)

On Sat, Sep 30, 2017 at 5:44 AM, Philip Jägenstedt <foo...@google.com> wrote:
testharness.js ought to be synced regularly, Quinten filed https://bugs.chromium.org/p/chromium/issues/detail?id=685854 some time ago about that.
On Sat, Sep 30, 2017 at 2:11 PM Robert Ma <robe...@google.com> wrote:
Thank you, Quinten!

Philip, lint is now up-to-date. However, testharness is not. I know our testharnessreport is home baked and cannot be synced. What about testharness?

On Sep 30, 2017 04:58, "'Philip Jägenstedt' via blink-infra" <blink...@chromium.org> wrote:
On Sat, Sep 30, 2017 at 12:03 AM 'Quinten Yearsley' via ecosystem-infra <ecosyst...@chromium.org> wrote:
Changes in the past couple weeks:

Import:
Export:
Awesome, does that mean that the lint is also updated? I've been secretly worrying about what will happen if it gets out of sync, so some way of keeping wpt tools more regularly in sync would be good.

On a related note, is testharness.js in sync now as well?

Thanks Robert :-)

Other updates:
  • BlinkOn8 happened last week, and there seems to be continued general interest in wpt (as evidenced by number of people attending the talk about wpt).
  • In Q4, the ecosystem infra OKRs around import and export will be about latency: In general, there is a goal is that import latency should be less than 12 hours, and export should be in less than 1 hour.
  • Also, I don't plan to continue sending out updates in this format in Q4, although there are still exciting changes in the future. Some recent changes can still be seen by checking out recent code changes in the importer/exporter code (webkitpy/w3c/).

--
You received this message because you are subscribed to the Google Groups "ecosystem-infra" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ecosystem-infra+unsubscribe@chromium.org.

--
You received this message because you are subscribed to the Google Groups "blink-infra" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-infra+unsubscribe@chromium.org.
Reply all
Reply to author
Forward
0 new messages