Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[EventTiming] Allow spurious inputs when looseCount is true #23925

Merged
merged 2 commits into from Jun 4, 2020
Merged

[EventTiming] Allow spurious inputs when looseCount is true #23925

merged 2 commits into from Jun 4, 2020

Commits on Jun 3, 2020

  1. [EventTiming] Allow spurious inputs when looseCount is true 

    This CL is a tentative fix for some flaky tests. An assert_equals to 0
is sometimes failing, presumably because the test itself may cause some
inputs to occur. Hence, we only check that eventCounts is 0 when the
|looseCount| variable is set to false.

Bug: 1074048
Change-Id: I989ccdb7cb469ff24132bf17a3da9a43264ae6ed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225293
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774650}
    @npm1 @chromium-wpt-export-bot
    npm1 authored and chromium-wpt-export-bot committed Jun 3, 2020
    Copy the full SHA
    5f8150f View commit details
    Browse the repository at this point in the history

  2. Give two event-timing tests long timeout

    @Hexcles
    Hexcles committed Jun 3, 2020
    Copy the full SHA
    7825646 View commit details
    Browse the repository at this point in the history