New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 631021 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

webkit_unit_tests AnimationCompositorAnimationsTest.ConvertTimingForCompositorIterationCount is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Jul 25 2016

Issue description

"webkit_unit_tests (with patch)" is flaky.

This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label.

We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyKQsSBUZsYWtlIh53ZWJraXRfdW5pdF90ZXN0cyAod2l0aCBwYXRjaCkM.



This flaky test/step was previously tracked in  issue 627927 .
 

Comment 1 by mark@chromium.org, Jul 25 2016

Components: Blink>Animation
Status: Available (was: Untriaged)
Summary: webkit_unit_tests AnimationCompositorAnimationsTest.ConvertTimingForCompositorIterationCount is flaky (was: "webkit_unit_tests (with patch)" is flaky)
AnimationCompositorAnimationsTest.ConvertTimingForCompositorIterationCount uses EXPECT_DEATH. Death tests from multi-threaded programs are dangerous. Revision history shows that this test has a history of being flaky and disabled. The death test aspect should be removed.
Cc: mit...@mithis.com
Owner: dstockwell@chromium.org
Status: Assigned (was: Available)
CC the author of the test, who I'm not sure is still active on chrome.

Assigning to the reviewer of the test, who I think still works on this kind of area.


Comment 3 by suzyh@chromium.org, Jul 25 2016

Cc: -mit...@mithis.com tansell@chromium.org
Components: -Tests>Flaky
Labels: Update-Weekly
Owner: suzyh@chromium.org
I'll take a look at this one.
Project Member

Comment 4 by bugdroid1@chromium.org, Jul 26 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/0bc11b2ac870eb60d74f0f56337703ff6d4f1c80

commit 0bc11b2ac870eb60d74f0f56337703ff6d4f1c80
Author: suzyh <suzyh@chromium.org>
Date: Tue Jul 26 01:27:11 2016

Remove death test in CompositorAnimationsTest

AnimationCompositorAnimationsTest.ConvertTimingForCompositorIterationCount
contains an EXPECT_DEATH test which checks that
CompositorAnimations::convertTimingForCompositor hits an assertion failure if
passed a Timing object with a value of -1 for iterationCount. This test is
probably included because -1 is a valid value for the equivalent field in the
output CompositorTiming object.

However, EXPECT_DEATH is flaky and dangerous in a multi-threaded context. Since
we're not gaining much by having this test, this patch removes it.

BUG= 631021 

Review-Url: https://codereview.chromium.org/2180973003
Cr-Commit-Position: refs/heads/master@{#407674}

[modify] https://crrev.com/0bc11b2ac870eb60d74f0f56337703ff6d4f1c80/third_party/WebKit/Source/core/animation/CompositorAnimationsTest.cpp

Comment 5 by suzyh@chromium.org, Jul 26 2016

Status: Fixed (was: Assigned)
Labels: hotlist-infra-opportunity

Sign in to add a comment