Robert Ma

Turns out wptrunner does not support Python 3 :( , which is an important new piece of information to make the decision.

@foolip WPT tools can definitely run in another process (and probably should). However, @lukebjerring provided one more data point yesterday that some AppEngine stuff he's hacking on is not py3-compatible....

Wow, OK, so even though AppEngine supports Python 3 in prod (flexible environment), its SDK is still py2-only. I guess this is a deal breaker. Let's change everything to Python...

I think there is, and there will still be (in sister projects, too) because unfortunately Python 3 still isn't supported by all infrastructures (e.g. AppEngine Standard). I think, as a...

cc @lukebjerring as he mentioned seeing some errors when setting up the new docker dev environment. Not sure if it's the same issue.

Thanks for filing the issue, Mike. I think we have many consensus here: * Test runner shouldn't do any fancy processing of the results. _I think_ the final product of...

BTW, @jugglinmike which tool do you use to make the ASCII flow charts? :)

The idea is to set a long enough expiration (e.g. a week or month) for the results on the runner side, so that premature deletion won't be a problem in...

One thing I feel a bit uneasy about is to give runners write access to the canonical storage. We could set permissions properly to prevent deletion and modification, but we...

It's more about the transformation/marshalling for the frontend to consume than validation. We already have some internal/third-party experimental running infra that's not using run.py and we would like to make...