W3C home > Mailing lists > Public > public-test-infra@w3.org > April to June 2018

Re: A new GitHub organization for web-platform-tests

From: Mike Pennisi <mike@bocoup.com>
Date: Wed, 4 Apr 2018 11:52:17 -0400
To: public-test-infra@w3.org
Message-ID: <62b5d381-0517-3260-fc09-b69a0219350a@bocoup.com>
> What would a structure that doesn't mix tests and infrastructure look
> like?  Two subdirectories?

Due to James' feedback, it probably doesn't matter. But since you ask:
we have a bunch of non-test directories that could remain at the top
level or be re-organized. The latter would be more disruptive, of
course, but this suggestion is couched by, "if we're already asking
consumers to accommodate breaking changes..."

> I don't think there's a reason to link together the proposal to move
> to an independent Github organization (which seems to have rough
> consensus already), and your (rather more vague) proposal.

My rationale was that since the organization change will interrupt the
normal workflow for WPT, it may be a good opportunity to include
additional changes that we've previously deferred out of reluctance to
disturb consumers.

> Any mass move like this would be disruptive for gecko.

Thanks, James. This is reason enough to drop the proposal. Just wanted
to make sure we weren't missing out on an opportunity to improve WPT
still further :)

On 04/04/2018 05:31 AM, James Graham wrote:
> On 04/04/2018 07:18, Philip Jägenstedt wrote:
>> What would a structure that doesn't mix tests and infrastructure look
>> like?
>> Two subdirectories?
>
> Any mass move like this would be disruptive for gecko. Although we do
> have support for moving metadata files when downstreaming, I don't
> particularly want to find out all the edge cases that occur when every
> test is moved. Moving the tooling is not well supported since various
> paths are hardcoded (so that e.g. wptrunner ends up on the Python path
> when running gecko-specific tooling). It would also cause merge
> conflicts with every local change, and break tests relying on absolute
> paths. I can't imagine it would be less than a week of work to fix all
> the fallout from such a change, and more than likely there would be
> subtle breakage not noticed for a long time.
>
> In the absence of strong evidence that the current setup is causing
> problems at the same scale as the disruption any move would cause, I
> am very reluctant to start making large-scale changes to the
> organisation of the repository.
>
Received on Wednesday, 4 April 2018 15:52:47 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 4 April 2018 15:52:48 UTC