- From: jgraham <web-platform-tests-notifications@w3.org>
- Date: Tue, 17 Jan 2017 21:36:23 GMT
- To: public-web-platform-tests-notifications@w3.org
So the problem with flaky tests is that they will tend to just be disabled when you import them, so you end up without coverage for either the original issue or the flakiness. So unfortunately it's probably better to work around the issue in the test. The counterargument in this case is that Chrome may not import the test immediately anyway so hopefully the bug will be fixed by the time that the test is imported into the Blink repo. Basically I'm happy for you to take either path in this specific case. View on GitHub: https://github.com/w3c/web-platform-tests/pull/4539#issuecomment-273307542
Received on Tuesday, 17 January 2017 21:36:35 UTC