On Wednesday, August 24, 2016 at 7:04:28 PM UTC+1, Jim Blandy 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.
And to follow on, given I didn't explicit state this befor
> On 24/08/16 18:12, Lars Bergstrom wrote:
> > Any opinions or other ideas here?
Yes. We stop relying on the build system entirely, and move to having
csswg-test instead of css-test-built in repo. As hinted at, there's been
ongoing work to make it possible to run all the CSS tests with wptserve
Do you both object just as much if ./mach puts the tests in tree via
another mechanism than git clone of servo/servo? If we combined this
with having our _mozilla tests in servo/servo until they are
upstreamed, this would make contributing new tests just as easy as it
is now and fix the repo integr
> On Aug 24, 2016, at 09:12, Lars Bergstrom wrote:
>
> Currently, the GitHub Servo repository has 134,062 files... 131,477 of
> which are in the tests/ directory. Of those, 102,871 are in the CSS WG
> tests. I know it's not a perfect measure, but that's also 862megs of
> the 1.132gb of disk space
On 25/08/16 08:56, Ms2ger wrote:
On 24/08/16 18:12, Lars Bergstrom wrote:
Currently, the GitHub Servo repository has 134,062 files... 131,477 of
which are in the tests/ directory. Of those, 102,871 are in the CSS WG
tests. I know it's not a perfect measure, but that's also 862megs of
the 1.132gb
On 24/08/16 18:12, Lars Bergstrom wrote:
> Currently, the GitHub Servo repository has 134,062 files... 131,477 of
> which are in the tests/ directory. Of those, 102,871 are in the CSS WG
> tests. I know it's not a perfect measure, but that's also 862megs of
> the 1.132gb of disk space usage reporte
On 24/08/16 20:04, Jim Blandy 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.
In short: yes.
As I understand, the current build system is designed so that the build
outp
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
-
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 wrote:
> On 24/08/16 18:37, Simon Sapin wrote:
>
>> Some files (some of them relativel
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.
--
Si
On 24/08/16 18:12, Lars Bergstrom wrote:
Currently, the GitHub Servo repository has 134,062 files... 131,477 of
which are in the tests/ directory. Of those, 102,871 are in the CSS WG
tests. I know it's not a perfect measure, but that's also 862megs of
the 1.132gb of disk space usage reported by `
Currently, the GitHub Servo repository has 134,062 files... 131,477 of
which are in the tests/ directory. Of those, 102,871 are in the CSS WG
tests. I know it's not a perfect measure, but that's also 862megs of
the 1.132gb of disk space usage reported by `du` on macOS for a Servo
checkout.
So, I'd
12 matches
Mail list logo
