New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 3 users
Status: WontFix
Owner: ----
Closed: Sep 4
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Sign in to add a comment
SharedExclusiveLockTest.TestSharedShared is flaky
Project Member Reported by, May 9 2014 Back to list
What steps will reproduce the problem?
1. Run libjingle_unittests

What is the expected result?

What do you see instead?
It flakes:

 RUN      ] SharedExclusiveLockTest.TestSharedShared
e:\b\build\slave\win\build\src\talk\base\ error: Expected: (reader0.waiting_time_in_ms()) <= (kNoWaitThresholdInMs), actual: 16 vs 10
[  FAILED  ] SharedExclusiveLockTest.TestSharedShared (125 ms)

Please use labels and text to provide additional information.

Comment 1 by, May 26 2014
Owner: ----
Status: Available
Project Member Comment 2 by, Nov 13 2014
Comment 3 by, Dec 17 2014
Labels: Area-PeerConnection
Project Member Comment 4 by, Jan 6 2015
Labels: EngTriaged IceBox
Looks like we need to rewrite this test.
Project Member Comment 5 by, Jan 6 2015
Project Member Comment 6 by, Jan 7 2015
This test is a part of the rtc_unittests executable these days.
I suggest we exclude it from Dr memory runs (i.e. add it to
Project Member Comment 8 by, Nov 8 2016
Labels: Pri-3
Project Member Comment 9 by, Dec 14 2016
Owner: ----
Project Member Comment 10 by, Sep 4
Status: WontFix
Assuming obsolete
Sign in to add a comment