Layout tests related to code caches timeout on Webkit Linux Trusty MSAN |
||||
Issue descriptionFollowing tests timeout on Webkit Linux Trusty MSAN builds: http/tests/devtools/isolated-code-cache/cross-origin-test.js http/tests/devtools/isolated-code-cache/same-origin-test.js They use devtools timeline which is slow and also navigate multiple times which makes them further slow.
,
Nov 14
,
Nov 14
I can't find tests by the name of "cross-origin-test" or "same-origin-test" by using codesearch or manually trying to run a test with those names: https://cs.chromium.org/search/?q=cross-origin-test.js&sq=package:chromium&type=cs third_party/blink/tools/run_web_tests.py http/tests/devtools/isolated-code-cache/same-origin-test.js Could you help me find those tests?
,
Nov 14
That cl got reverted. I am trying to reland it now by updating the expectations. Here is the cl: https://chromium-review.googlesource.com/c/chromium/src/+/1329561/2.
,
Nov 21
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8164901d8d42f2c4ef636c3068350ce98940b97b commit 8164901d8d42f2c4ef636c3068350ce98940b97b Author: Lukasz Anforowicz <lukasza@chromium.org> Date: Wed Nov 21 19:30:38 2018 Extend isolated-code-cache=[Slow] to the not-site-per-process suite. Bug: 907402 , 902685 Change-Id: Ifa530668be9f322a2ae5d92692298c20f98da828 Reviewed-on: https://chromium-review.googlesource.com/c/1347089 Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Commit-Queue: Ćukasz Anforowicz <lukasza@chromium.org> Cr-Commit-Position: refs/heads/master@{#610156} [modify] https://crrev.com/8164901d8d42f2c4ef636c3068350ce98940b97b/third_party/WebKit/LayoutTests/SlowTests [modify] https://crrev.com/8164901d8d42f2c4ef636c3068350ce98940b97b/third_party/WebKit/LayoutTests/TestExpectations
,
Nov 21
,
Nov 21
mythria@ lukasza@ now that the test has been relanded, is this still an issue?
,
Nov 21
Yes, I think the test is still slow - see https://bugs.chromium.org/p/chromium/issues/detail?id=907402#c7 (which provides data from today and yesterday, which I think comes from *after* the test has been relanded, right?).
,
Dec 4
|
||||
►
Sign in to add a comment |
||||
Comment 1 by lushnikov@google.com
, Nov 12