Keeping in sync with testharness.js?

[foolip]

https://github.com/web-platform-tests/editor/blob/master/wwwroot/bin/testharness.js is a copy of wpt's testharness.js, which needs to be kept in sync. Is there a way to keep this dependency fresh?

[snuggs]

@foolip perhaps a githook with a curl?
There is a git archive that does just this ! HOWEVER... disabled on github :-(

As a last resort there is git SVN. Although it feels like eating soup with a fork it does work.

Lastly I don't mind working on this as i've had to do the same for testharness.js in the past (using curl). But i'm not very familiar with this project on WPT.

Your thoughts..

[foolip]

One option would be to reference https://wpt.live/resources/testharness.js.

Another is to copy it from the wpt in a build step.

[snuggs]

@foolip 👍 for copy (& commit). FWIW Have attempted your first suggestion before and was up all night on false errors from a server being down for maintenance. Not saying this isn't a possibility with latter method. But at least possibility of earlier discovery.

Thanks!

[foolip]

@stephenmcgruer do we have uptime monitoring of wpt.live and some kind of SLA, if someone does want to depend on it being "always" up?

[stephenmcgruer]

To answer the latter first, we do not currently have an SLA for wpt.live and I don't expect us to add one. It is a best-effort system currently. That said I'm surprised to hear of the report of the server being down (I don't expect much if any downtime); @snuggs do you know when this happened?

Wrt monitoring, we have basic GCP monitoring but nothing specific setup yet. cc @LukeZielinski as a vague fyi that this might fit into the productionization effort (as part of best-practices for our GCP hosted services).