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

Issue 615450 link

Starred by 1 user
Status: Fixed
Owner:
█ yzshen@chromium.org
Last visit > 30 days ago
Closed: May 2016
Cc:
█ yzshen@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"AssociatedInterfaceTest.MultiThreadAccess" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, May 27 2016 
"AssociatedInterfaceTest.MultiThreadAccess" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyNAsSBUZsYWtlIilBc3NvY2lhdGVkSW50ZXJmYWNlVGVzdC5NdWx0aVRocmVhZEFjY2Vzcww.

Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs

Comment 1 by ymalik@chromium.org, May 31 2016

Owner: yzshen@chromium.org
Status: Available (was: Untriaged)
@yzshen I see that you have made recent changes to the test. Can you help triage this?

The test often crashes and sometimes fails expectations.

error: Value of: receivers[0].values().size()

  Actual: 379

Expected: static_cast<size_t>(kMaxValue / 2)

Which is: 500


Will disable

Comment 2 by yzshen@chromium.org, May 31 2016

Status: Started (was: Available)
Project Member

Comment 3 by bugdroid1@chromium.org, May 31 2016 

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

commit 2d8099320a01bc7a8fa0a9fd77859882b24a198e
Author: ymalik <ymalik@chromium.org>
Date: Tue May 31 17:51:44 2016

Disable AssociatedInterfaceTest.MultiThreadAccess

This test has been flaky on the buildbots from the past few days. Disabling
until root cause has been determined.

BUG= 615450 
TBT=yzshen@chromium.org

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

[modify] https://crrev.com/2d8099320a01bc7a8fa0a9fd77859882b24a198e/mojo/public/cpp/bindings/tests/associated_interface_unittest.cc

Comment 4 by roc...@chromium.org, May 31 2016

Cc: yzshen@chromium.org
 Issue 578704  has been merged into this issue.
Project Member

Comment 5 by bugdroid1@chromium.org, May 31 2016 

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

commit b27570bcea1c59859ca6690e0bcd1e3a8d7125c1
Author: yzshen <yzshen@chromium.org>
Date: Tue May 31 19:01:04 2016

Mojo C++ bindings: fix AssociatedInterfaceTest.MultiThreadAccess.

In this test, each receiver receives values from two senders running in parallel. Previously, the test didn't wait for all data from both senders.

BUG= 615450 

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

[modify] https://crrev.com/b27570bcea1c59859ca6690e0bcd1e3a8d7125c1/mojo/public/cpp/bindings/tests/associated_interface_unittest.cc

Comment 6 by yzshen@chromium.org, May 31 2016

Status: Fixed (was: Started)
Mark it as fixed. Will keep an eye on it and reopen if new failures are found.
►

Sign in to add a comment