Flaky timeouts of virtual/enable_wasm/http/tests/wasm/wasm_remote_postMessage_test.https.html in webkit_layout_tests |
|||
Issue descriptionSeen in this tryjob: https://luci-milo.appspot.com/buildbot/tryserver.chromium.win/win_chromium_rel_ng/533513 21:00:48.625 652 worker/0 but timeouts are also seen on the flakiness dashboard: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=webkit_layout_tests&tests=wasm_remote_postMessage_test although not on the Windows testers, which is the platform where I saw the flake. Timeouts are seen on WebKit Linux Trusty (dbg), WebKit Mac10.10..10.12, etc. Looks like the test may be marked as timing out in TestExpectations; I didn't check. Brad, could you please find someone to triage this? Log excerpt: virtual/enable_wasm/http/tests/wasm/wasm_remote_postMessage_test.https.html output stderr lines: 21:00:48.625 652 [8444:4868:0914/210042.616:33513257:ERROR:direct_composition_surface_win.cc(1095)] Failing to detect HDR, couldn't retrieve D3D11 device from ANGLE. 21:00:48.625 652 [8444:4868:0914/210042.619:33513257:INFO:media_foundation_video_encode_accelerator_win.cc(335)] Windows versions earlier than 8 are not supported. 21:00:48.627 9128 [11705/11781] virtual/enable_wasm/http/tests/wasm/wasm_remote_postMessage_test.https.html failed unexpectedly (test timed out) 21:00:48.626 652 worker/0 killing primary driver 21:00:48.627 652 worker/0 killing secondary driver 21:00:48.627 652 worker/0 virtual/enable_wasm/http/tests/wasm/wasm_remote_postMessage_test.https.html failed: 21:00:48.627 652 worker/0 test timed out
,
Sep 18 2017
,
Sep 18 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e840cdf0a3fa4e3c2da24dc4bd9c38d854c7cda5 commit e840cdf0a3fa4e3c2da24dc4bd9c38d854c7cda5 Author: Max Morin <maxmorin@chromium.org> Date: Mon Sep 18 10:31:05 2017 Expectation for flaky wasm_remote_postMessage_test.https.html Bug: 765738 Change-Id: Id484c55f7bd6000a6d088ff207e2ee3372c0a4df TBR: mtrofin Reviewed-on: https://chromium-review.googlesource.com/670621 Reviewed-by: Max Morin <maxmorin@chromium.org> Commit-Queue: Max Morin <maxmorin@chromium.org> Cr-Commit-Position: refs/heads/master@{#502550} [modify] https://crrev.com/e840cdf0a3fa4e3c2da24dc4bd9c38d854c7cda5/third_party/WebKit/LayoutTests/TestExpectations
,
Sep 20 2017
Looking. It's not reproductible locally (or not yet), and looking at the test, we may just wait forever in it. I'll add a timeout to start.
,
Sep 26 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/cc1c476f83ca19d8013cd195b1c35601cc5745a6 commit cc1c476f83ca19d8013cd195b1c35601cc5745a6 Author: Mircea Trofin <mtrofin@chromium.org> Date: Tue Sep 26 20:08:33 2017 [wasm] Fail remote post message test if about:blank can't open Instead of waiting until the test harness timeouts the test, we wait for a set period of time for the about:blank window to open, after which we fail the test. Bug: chromium:765738 Change-Id: I8635c19683a3791801bc3e75a3fc3bf16872b6f2 Reviewed-on: https://chromium-review.googlesource.com/676283 Commit-Queue: Brad Nelson <bradnelson@chromium.org> Reviewed-by: Brad Nelson <bradnelson@chromium.org> Cr-Commit-Position: refs/heads/master@{#504467} [modify] https://crrev.com/cc1c476f83ca19d8013cd195b1c35601cc5745a6/third_party/WebKit/LayoutTests/http/tests/wasm/wasm_remote_postMessage_test.https.html
,
Jun 13 2018
reassigning to me since mtrofin left the project. It appears this test is still flaky. |
|||
►
Sign in to add a comment |
|||
Comment 1 by bradnelson@chromium.org
, Sep 18 2017Owner: mtrofin@chromium.org