Issue metadata
Sign in to add a comment
|
Flaky failure in http/tests/dom/promise-rejection-events.html (non-deterministic console errors) |
||||||||||||||||||||||||
Issue descriptionIn the latest web-platform-tests import CL (https://codereview.chromium.org/2648173006), I observed the following output from this test in some try jobs: Start of test output: CONSOLE ERROR: line 15: Uncaught (in promise) Error CONSOLE ERROR: line 24: Uncaught (in promise) Error CONSOLE ERROR: line 541: Uncaught (in promise) Error CONSOLE ERROR: line 560: Uncaught (in promise) Error CONSOLE ERROR: line 577: Uncaught (in promise) Error CONSOLE ERROR: line 600: Uncaught (in promise) Error CONSOLE ERROR: line 625: Uncaught (in promise) Error CONSOLE ERROR: line 667: Uncaught (in promise) Error CONSOLE ERROR: line 2684: Uncaught TypeError: Cannot read property 'message' of undefined CONSOLE ERROR: line 700: Uncaught (in promise) undefined CONSOLE ERROR: line 2684: Uncaught TypeError: Cannot read property 'message' of undefined CONSOLE ERROR: line 767: Uncaught (in promise) undefined CONSOLE ERROR: line 62: Uncaught (in promise) Error CONSOLE ERROR: line 120: Uncaught (in promise) Error CONSOLE ERROR: line 131: Uncaught (in promise) Error CONSOLE ERROR: line 157: Uncaught (in promise) Error CONSOLE ERROR: line 35: Uncaught (in promise) Error CONSOLE ERROR: line 2684: Uncaught TypeError: Cannot read property 'message' of undefined CONSOLE ERROR: line 703: Uncaught (in promise) undefined CONSOLE ERROR: line 2684: Uncaught TypeError: Cannot read property 'message' of undefined CONSOLE ERROR: line 735: Uncaught (in promise) undefined CONSOLE ERROR: line 48: Uncaught (in promise) Error CONSOLE ERROR: line 78: Uncaught (in promise) Error CONSOLE ERROR: line 98: Uncaught (in promise) Error CONSOLE ERROR: line 142: Uncaught (in promise) Error CONSOLE ERROR: line 15: Uncaught (in promise) Error CONSOLE ERROR: line 24: Uncaught (in promise) Error CONSOLE ERROR: line 541: Uncaught (in promise) Error CONSOLE ERROR: line 560: Uncaught (in promise) Error CONSOLE ERROR: line 577: Uncaught (in promise) Error CONSOLE ERROR: line 600: Uncaught (in promise) Error CONSOLE ERROR: line 625: Uncaught (in promise) Error CONSOLE ERROR: line 667: Uncaught (in promise) Error CONSOLE ERROR: line 62: Uncaught (in promise) Error CONSOLE ERROR: line 120: Uncaught (in promise) Error CONSOLE ERROR: line 131: Uncaught (in promise) Error CONSOLE ERROR: line 157: Uncaught (in promise) Error CONSOLE ERROR: line 35: Uncaught (in promise) Error CONSOLE ERROR: line 48: Uncaught (in promise) Error CONSOLE ERROR: line 78: Uncaught (in promise) Error CONSOLE ERROR: line 98: Uncaught (in promise) Error CONSOLE ERROR: line 142: Uncaught (in promise) Error This is a testharness.js-based test. Harness Error. harness_status.status = 1 , harness_status.message = ... The order of these errors was different on different runs. I think that the reason for these error messages may be that testharness.js was changed.
,
Feb 9 2017
It's a testharness test, so the order of console messages does not matter
,
Feb 9 2017
,
Feb 9 2017
I think there's probably something about the way that the test is written that will stop it from generating these errors. If it turns out these errors are actually intended or unavoidable, then I think it's possible to just turn off printing of errors for this test, as in http://crrev.com/2680863006.
,
Feb 9 2017
This is the same as the problem being discussed in https://bugs.chromium.org/p/chromium/issues/detail?id=679742, where WPTs should not be asserting based on console output, but instead only on the assertions. BTW jochen@, I've been trying to submit these upstream at https://github.com/w3c/web-platform-tests/pull/2388 but Chrome no longer passes allow-crossorigin.html. Also for some reason the serviceworker version gives a harness status of error.
,
Feb 9 2017
Yeah, saw your comment on the gh issue... Still on my backlog :/
,
Feb 10 2017
looking at the gh issue, seems like you figured it out?
,
Feb 10 2017
No... I've gotten things looking better in general, but the two outstanding mysteries are Chrome not passing allow-crossorigin.html and the service worker version giving a harness error. I'll bang on the latter some more myself but the former could use your help.
,
Feb 15 2017
,
Mar 13 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/576f6e58b5929f2d38bd05326758dc1a07513b00 commit 576f6e58b5929f2d38bd05326758dc1a07513b00 Author: qyearsley <qyearsley@chromium.org> Date: Mon Mar 13 21:28:45 2017 Remove flaky test expectations with update-test-expectations. Flakiness dashboard: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=webkit_tests&tests=virtual/wheelscrolllatching/fast/events/wheel/wheel-scroll-latching-on-scrollbar.html,media/video-layer-crash.html,http/tests/dom/promise-rejection-events.html,virtual/mojo-loading/http/tests/dom/promise-rejection-events.html,external/wpt/html/syntax/parsing/template/creating-an-element-for-the-token/template-owner-document.html,fast/frames/location-change-no-file-access.html,virtual/threaded/compositing/visibility/overlays-persist-on-navigation.html BUG=526463, 637255 , 685778 ,626703,691423,695352 Review-Url: https://codereview.chromium.org/2743223002 Cr-Commit-Position: refs/heads/master@{#456492} [modify] https://crrev.com/576f6e58b5929f2d38bd05326758dc1a07513b00/third_party/WebKit/LayoutTests/TestExpectations |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by qyears...@chromium.org
, Jan 27 2017