- From: jugglinmike <web-platform-tests-notifications@w3.org>
- Date: Mon, 03 Apr 2017 18:51:22 GMT
- To: public-web-platform-tests-notifications@w3.org
@jeffcarp It would create more work for me/my reviewers down the line, but I would be able to continue working even if the commit is removed from Chromium's `master` branch. More importantly, though: it would not actually solve the problem. I've demonstrated that the test in question already behaves inconsistently in WPT `master`, so even if Chromium's automated process reverts this patch, the flakiness will persist. (roping @rbyers and @foolip in here) I wasn't aware of that aspect of Chromium's WPT Sync process. This may be a more fundamental problem due to the following aspects of the current set up: - Chromium rejects patches that are not merged to WPT - WPT rejects patches that are inconsistent in Firefox or Chrome (this is soon to include Edge and Safari, too) Unless I'm mistaken, this means that Chromium cannot contribute tests that demonstrates flaky behavior in any browser. Similarly (as in the case of this patch), it cannot modify "resource" files that happen to be used by such flaky tests. This is news to me. Does it concern you folks at all, or is it too rare to worry about? View on GitHub: https://github.com/w3c/web-platform-tests/pull/5307#issuecomment-291237939
Received on Monday, 3 April 2017 18:51:34 UTC