W3C home > Mailing lists > Public > www-archive@w3.org > February 2017

Re: Building CSS test suites from web-platform-tests

From: Geoffrey Sneddon <me@gsnedders.com>
Date: Fri, 24 Feb 2017 19:02:28 +0000
Message-ID: <CAHKdfMhNguOFo7J-cp-Pya5a2Enq0wUy4fjALQ_0Q5rugFyhZA@mail.gmail.com>
To: Peter Linss <peter@linss.com>
Cc: www-archive <www-archive@w3.org>
On Fri, Feb 24, 2017 at 6:41 PM, Peter Linss <peter@linss.com> wrote:
> On Feb 24, 2017, at 9:59 AM, Geoffrey Sneddon <me@gsnedders.com> wrote:
> Hi,
> I think we're close to being ready to merge the two test suites now.
> The one item on the to-do list that's out of my control is making sure
> the test harness still gets the test suites; as agreed before the CSS
> build system is just remaining pretty much as-is in the short term,
> hence it's mostly making sure the test harness pulls from git and
> builds from there.
> https://github.com/w3c/web-platform-tests/tree/csswg_test_merged has a
> merged tree (note, however, that I am intermittently force-pushing to
> that branch; the merge commit will always be the top of it).
> Notably, the css subdirectory is essentially just csswg-test, though
> note that w3ctestlib and apiclient are now git submodules of the repo.
> There's now a css/build-css-testsuites.sh which should probably be the
> recommended way to build the testsuite given it deals with
> requirements. Of course, you can always just cd css; python
> tools/build.py and then look in dist.
> Obviously you don't want to actually make the web-platform-tests
> script the active script until we've actually done the merge, but do
> you have any idea of by when you could alter the script for it?
> /gsnedders
> So long as the build output from wpt is identical to what’s being produced
> in csswg-test I can do the switchover anytime, shouldn’t take more than a
> few minutes.
> I’m probably going to be out and about most of the day Saturday, but I can
> do it just about any other time, including this afternoon.
> Worst case if I don’t get to it for a day or so is that the harness just has
> stale tests until I update it, so whenever you’re ready to flip the switch,
> go for it and let me know when it’s done.
> I’ll also turn off commits to the hg repo at the same time and make Shepherd
> read-only (just flipping some permission bits).
> What’s the plan for github.com/w3c/csswg-tests again? Is it going to be
> deleted or just made read-only?

We're still a few weeks off; I expect I'll do it on some Monday
afternoon UTC in case of any auto-syncing scripts going crazy with
thousands of files!

My plan for csswg-test is to make it admin-push only, keep everything
as-is, and add a new "deprecated" branch as the default branch with
just a README.md so the GitHub home-page of it contains a link to
where to go.

Received on Friday, 24 February 2017 19:11:32 UTC

This archive was generated by hypermail 2.3.1 : Friday, 24 February 2017 19:11:33 UTC