[dev-servo] Proposal: TLS library for Servo

Servo has been using the cryptographic library, OpenSSL (via the Hyper library) for securing communications. As the project transitions to shipping nightly builds and hopefully products, we need to make a more explicit decision about our library usage. As a web browser, there’s a high standard to

Re: [dev-servo] Moving style out of tree as an alternative to frankenbuild?

On 25/08/16 20:55, Manish Goregaokar wrote: I suspect they won't be too bad, and once stylo settles down a bit there won't be many breaking changes. I believe this is not at all the case. We gave up a long time ago on reducing the API surface of the style crate (what’s visible from other

Re: [dev-servo] The size of the tests/ directory

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

Re: [dev-servo] The size of the tests/ directory

> 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

Re: [dev-servo] Moving style out of tree as an alternative to frankenbuild?

On Thu, Aug 25, 2016 at 1:55 PM, Manish Goregaokar wrote: > > There are a lot of issues with this. I agree that there are challenges with mirroring the root Servo repository into m-c, but I'd like to make sure we mention some of the positives that we get from it: - Having

Re: [dev-servo] Moving style out of tree as an alternative to frankenbuild?

> Your proposal scares me in the sense that (if I read it well) it would > be at least temporarily allowing changing the style system without > gating on Servo. There are architectural changes to the style system > that work for Gecko, but would completely break Servo. This would obviously be a

Re: [dev-servo] Moving style out of tree as an alternative to frankenbuild?

Hi Manish, Your proposal scares me in the sense that (if I read it well) it would be at least temporarily allowing changing the style system without gating on Servo. There are architectural changes to the style system that work for Gecko, but would completely break Servo. Right now landing a

Re: [dev-servo] Moving style out of tree as an alternative to frankenbuild?

> The other proposal includes making sure Gecko related stylo changes > don't break Servo, but this does not. It seems easy enough to add > Servo's test suite to the m-c side CI, so I would propose to add that > to your proposal. That means we only have to resolve conflicts until > CI is fully

Re: [dev-servo] Moving style out of tree as an alternative to frankenbuild?

> The downsides of this model are: > > Servo has to periodically sync with style and resolve conflicts. I volunteer > as tribute to do these. I suspect they won't be too bad, and once stylo > settles down a bit there won't be many breaking changes. The other proposal includes making sure Gecko

[dev-servo] Moving style out of tree as an alternative to frankenbuild?

Hi, The current situation with the m-c vendoring for stylo is to put all of stylo in-tree and have an autolander dance between homu (or at least Servo buildbot) and the Gecko autolander that ensures that changes to servo/servo or m-c are always mirrored and fully tested, on both ends. There are

Re: [dev-servo] The size of the tests/ directory

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

Re: [dev-servo] The size of the tests/ directory

> 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

Re: [dev-servo] The size of the tests/ directory

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

Re: [dev-servo] The size of the tests/ directory

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