Thanks for doing this! I recently struggled to run some tests before realizing that they depended on geckodriver, which wasn't built by default. Assuming this didn't negatively impact build times, I'm glad to see a reduction in build config options.
On Wed, Sep 12, 2018 at 2:36 AM Andreas Tolfsen <a...@sny.no> wrote: > We have been building geckodriver on TaskCluster for a year and a > half, but it has so far not been enabled by default in local developer > builds. > > With a change that landed yesterday, geckodriver is included in the > default build configuration also for local developer builds. It > will not be built if --disable-tests is used. You can also explicitly > disable building it with --disable-geckodriver. > > geckodriver is our implementation of WebDriver, and in m-c, used > to back a subset of WPT tests. It is also a product in its own > right, in that it is used by several major websites that we care > about to help web compatibility. As we roll out support for more > platforms we expect to expand its in-tree use. > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
