Re: Please do NOT hand-edit web platform test MANIFEST.json files

On Tuesday, March 21, 2017 at 2:58:17 AM UTC+11, Boris Zbarsky wrote: > On 3/19/17 12:36 AM, Nils Ohlmeier wrote: > > Wouldn’t it make more sense to let the build system detect and reject/warn > > about (?) such a manual modification? > > That would be ideal, but there are some issues with doing

FYI: Tree Closing Window (TCW) this Saturday, March 25 0500-0930 PT

This will be a SOFT Tree Closure. As a reminder, that means: - jobs may burn - You are responsible for sheriffing your own jobs [TCW] Tree Closing Maintenance Window Mar 25, 05:00-09:30 PDT Trees will be closed for the duration of this

Cost of "duplicating" (or "worse") large parts of web-platform-tests

web-platform-tests has a nice feature which generates a bunch of boilerplate for you for dedicated worker tests and tests that can be run both in a window and a dedicated worker: http://web-platform-tests.org/writing-tests/testharness.html (Soon we'll also have it for just window tests, so you

Re: Please do NOT hand-edit web platform test MANIFEST.json files

On 3/19/17 12:36 AM, Nils Ohlmeier wrote: Wouldn’t it make more sense to let the build system detect and reject/warn about (?) such a manual modification? That would be ideal, but there are some issues with doing it. We tried adding a lint, but it was orange _all the time_ because the

Re: Switching to async/await from Task.jsm/yield

On 3/17/2017 5:19 PM, Dave Townsend wrote: One issue I have just spotted is that Task.jsm uses a JavaScript implementation of promises under the hood while async/await obviously uses our native implementation in the JS engine. You're inadvertently losing test coverage if you convert everything

[Firefox Desktop] Issues found: March 13th to March 17th

Hi everyone, Here's the list of new issues found and filed by the Desktop Release QA Team last week, *March 13 - March 17* (week 11). Additional details on the team's priorities last week, as well as the plans for the current week are available at: