- From: Dan Elphick <web-platform-tests-notifications@w3.org>
- Date: Thu, 05 Jan 2017 09:15:14 GMT
- To: public-web-platform-tests-notifications@w3.org
Sorry, my explanation of the need for this change wasn't very clear. I'm attempting to fix the behaviour in Chrome where setTimeout always waits at least 1ms even for setTimeout(..., 0). Only after doing this, did this test start to fail. The reason it fails is that the test completed before the font load failed and logged to the console, as previously this was taking somewhere between 0 and 1ms to occur. When the test runner compares the output to the expected output (https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/imported/wpt/WebIDL/current-realm-expected.txt), it finds that the CONSOLE ERROR message is missing. We could fix this by updating the expected output, but then we would still have a chance that the message could reappear possibly making the test flaky. I don't know how other browsers check for test success. If they are checking the console output and their tests are terminating after the log message is printed, then their golden files would need updating as well. View on GitHub: https://github.com/w3c/web-platform-tests/pull/4378#issuecomment-270597694
Received on Thursday, 5 January 2017 09:15:26 UTC