If tests are from upstream anyway, wouldn't it be easier to maintain them in a separate repository (or repositories)? Mach test can then be pointed at a specific fork/branch/tag/revision which it checks out before running the test. It may not even be necessary to pull tests downstream into Servo - we could just pull from the w3c repo directly and keep track only of the test expectations.
A current limitation of ./mach test-css is that it can only run tests from a specific directory inside the Servo project repo. This isn't ergonomic since CSS tests have to be merged into the w3c project before they can be pulled downstream into Servo. It's an issue which can be solved independently, but it would be more streamlined to work on tests in my branch of the w3c repo, and be able to test Servo against it as I go. Peter On 24 Aug 2016 7:04 p.m., "Jim Blandy" <jbla...@mozilla.com> wrote: > > Are any of these reductions things that could be contributed upstream? If > Mozilla's work could help the CSS WG test suite's other users, that would > be pretty great. > > On Wed, Aug 24, 2016 at 9:39 AM, Simon Sapin <simon.sa...@exyr.org> wrote: > > > On 24/08/16 18:37, Simon Sapin wrote: > > > >> Some files (some of them relatively large, like > >> reference/support/big-buck-bunny-240p.webm) are also duplicated across > >> multiple specs. > >> > > > > Looks like even within on spec, /support and /reference/support have some > > duplication. We should merge those too. > > > > > > -- > > Simon Sapin > > _______________________________________________ > > dev-servo mailing list > > dev-servo@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-servo > > > _______________________________________________ > dev-servo mailing list > dev-servo@lists.mozilla.org <dev-servo@lists.mozilla.org> > https://lists.mozilla.org/listinfo/dev-servo <https://lists.mozilla.org/listinfo/dev-servo> _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
