IntersectionObserver GC-dependent tests are flaky
authorajuma@chromium.org <ajuma@chromium.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Wed, 7 Nov 2018 21:00:34 +0000 (21:00 +0000)
committerajuma@chromium.org <ajuma@chromium.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Wed, 7 Nov 2018 21:00:34 +0000 (21:00 +0000)
commit6d7ffff642a8b352aff726e520af588b8b899074
treec291400331062050d94ef706529dd844f2feea92
parentc4321edaea2090429fe8ffc955b983d20c3fe50b
IntersectionObserver GC-dependent tests are flaky
https://bugs.webkit.org/show_bug.cgi?id=191387

Reviewed by Chris Dumez.

Make these tests more robust by triggering GC repeatedly inside a setInterval(). Having only a single call to
GC is potentially flaky, since that call will early-out and return immediately if a GC is already underway.

* intersection-observer/root-element-deleted.html:
* intersection-observer/target-deleted.html:

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@237939 268f45cc-cd09-0410-ab3c-d52691b4dbfc
LayoutTests/ChangeLog
LayoutTests/intersection-observer/root-element-deleted.html
LayoutTests/intersection-observer/target-deleted.html