Project: webrtc Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Issue 3318 SharedExclusiveLockTest.TestSharedShared is flaky
Starred by 3 users Project Member Reported by phoglund@webrtc.org, May 9 2014 Back to list
Status: Available
Owner: ----
Cc:
Components:
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment
What steps will reproduce the problem?
1. Run libjingle_unittests
2.
3.

What is the expected result?


What do you see instead?
It flakes:
http://chromegw/i/internal.client.webrtc/builders/Win32%20Debug/builds/1755/steps/libjingle_unittest/logs/stdio

 RUN      ] SharedExclusiveLockTest.TestSharedShared
e:\b\build\slave\win\build\src\talk\base\sharedexclusivelock_unittest.cc(170): 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 phoglund@google.com, May 26 2014
Owner: ----
Status: Available
Project Member Comment 2 by turaj@webrtc.org, Nov 13 2014
Comment 3 by vrk@webrtc.org, Dec 17 2014
Labels: Area-PeerConnection
Project Member Comment 4 by pthatcher@webrtc.org, Jan 6 2015
Labels: EngTriaged IceBox
Owner: pthatcher@webrtc.org
Looks like we need to rewrite this test.
Project Member Comment 5 by pthatcher@webrtc.org, Jan 6 2015
Cc: decurtis@webrtc.org
Project Member Comment 6 by kjellander@webrtc.org, 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 https://code.google.com/p/webrtc/source/browse/trunk/tools/valgrind-webrtc/gtest_exclude/rtc_unittests.gtest-drmemory.txt)
Project Member Comment 8 by pthatcher@webrtc.org, Nov 8 2016
Labels: Pri-3
Project Member Comment 9 by anatolid@webrtc.org, Dec 14
Cc: pthatcher@webrtc.org
Owner: ----
Sign in to add a comment