W3C home > Mailing lists > Public > public-test-infra@w3.org > January to March 2017

when automerging of tests goes awry

From: Patrick Kettner <patket@microsoft.com>
Date: Mon, 6 Mar 2017 23:40:33 +0000
To: "public-test-infra@w3.org" <public-test-infra@w3.org>
Message-ID: <BN1PR0301MB0657A8E6170D6BCCFFA11E6DDE2C0@BN1PR0301MB0657.namprd03.prod.outlook.com>
EHLO folks,
As we are all aware, the Chrome team recently began automatically upstreaming their layout tests with their new sync system. Todd Reifsteck, a coworker on perf and networking, brought an issue to my attention that feels like incorrect behavior that resulting because of it. A change is being proposed<https://github.com/w3c/navigation-timing/issues/59> to the navigation timing spec, which Chrome is wanting to implement. They have already implemented the feature, tests and all. As a result when it was merged into Chromium, tests included, it overrode the existing tests in WPT<https://github.com/w3c/web-platform-tests/commit/d24a86b138b2074f32a6f2bbd6ca5de445259dd3> via the sync. Now WPT is testing for behavior that is a breaking change from a previous level of the spec, before the change has even been made to the spec.

This feels wrong to me, but I was interested in what everyone else thought the behavior should be.

Received on Monday, 6 March 2017 23:41:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:34:13 UTC