jugglinmike

@reillyeon @Hexcles In light of https://github.com/w3c/web-platform-tests/issues/10452, I'm wondering if the desired functionality can also be enabled via `--enable-experimental-web-platform-features`. Do either of you know?

Got it. Thanks!

> @kereliuk, this is now done for Chrome, but not Firefox, right? [The results collector currently specifies the parameters mentioned above](https://github.com/web-platform-tests/results-collection/blob/8266cbb6235eeb0dd23bb1aa26bb3fb74cae5551/src/master/wpt_run_step.py#L79-L85), and, Chrome is [reported as passing some WebRTC tests...

It is currently running in Python 2, but this isn't a hard requirement because [Buildbot supports Python 3](http://docs.buildbot.net/current/manual/installation/requirements.html). I agree with @Hexcles's original assertion that using Python 3 would be...

We experienced this bug again today. It again occurred on a Safari trial, but this time, it was "chunk" number 77 of 100. This suggests that the problem is not...

Results aren't available for those files because we don't run those tests. Here's what the WPT CLI reports for the contents of that directory (pardon the debugging information): $ ./wpt...

[As discussed previously](https://github.com/w3c/wptdashboard/issues/234#issuecomment-365358893), the term "completeness" can be interpreted in a few ways. If we define "completeness" in terms of "tests executed" (as opposed to "subtests executed"), we can calculate...

> On wdspec, I agree that trying to run them over Sauce doesn't make sense, and > that we can just not run them using `--test-types=reftest,testharness` if > they aren't...

> Without it `async_test` with code not wrapped in `t.step_func` that throws > exceptions would go nowhere. Now, for `promise_test` things are different > because they run in serial, so...

> Do you mean just looking to see in which directories most of the problems > are? What answers couldn't we get by looking at the same information that is...