generic-library/webrtc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
6,738 Commits 1 Branch 0 Tags 108 MiB
9c58ea8d56
Commit Graph

4 Commits

Author SHA1 Message Date
kjellander@webrtc.org
940894d207 DrMemory: Excluding failing tests for Dr Memory Full 
PortAllocatorTest.TestEnableSharedSocketWithNat
fails in libjingle_p2p_unittest.
Example:
http://build.chromium.org/p/client.webrtc/builders/Win%20DrMemory%20Full/builds/2/steps/memory%20test%3A%20libjingle_p2p_unittest/logs/stdio
Previous experience tells me that disabling only this test
case will make another one in the same test suite fail,
so I'm blanked disabling the whole test.

TBR=phoglund
BUG=3158

Review URL: https://webrtc-codereview.appspot.com/11909004

git-svn-id: http://webrtc.googlecode.com/svn/trunk@5893 4adac7df-926f-26a2-2b94-8c16560cd09d
 2014-04-13 11:45:43 +00:00
kjellander@webrtc.org
41e8774113 DrMemory: Excluding failing tests for Dr Memory Full 
The PortTest.TestLocalToTurn of libjingle_p2p_unittest
and DtmfSenderTest.InsertDtmf of libjingle_peerconnection_unittest
failed in the first run on
http://build.chromium.org/p/client.webrtc/builders/Win%20DrMemory%20Full/
However, I cannot reproduce on my machine, so I'm disabling all
test cases of those tests, assuming the others might fail as well.

BUG=3158
TEST=None
TBR=phoglund

Review URL: https://webrtc-codereview.appspot.com/11889004

git-svn-id: http://webrtc.googlecode.com/svn/trunk@5891 4adac7df-926f-26a2-2b94-8c16560cd09d
 2014-04-12 19:53:06 +00:00
kjellander@webrtc.org
ffd242432d DrMemory: Suppress and exclude more tests to green up the full build. 
Exclude failing tests in libjingle tests and suppress
failures in modules_unittests.

Also exclude the following extremely slow tests to make it
possible to get a reasonable execution time for the bot:
* TestScaler.PointScaleTest (81573 ms)
* TestScaler.BiLinearScaleTest (1111554 ms)
* TestScaler.BoxScaleTest (1129625 ms)
* TestVp8Impl.BaseUnitTest (762598 ms)
* VideoProcessorIntegrationTest.ProcessNoLossChangeBitRate (342149 ms)

TBR=phoglund@webrtc.org
BUG=3158, 3183, 3184
TEST=Successful runs on local Windows box:
tools\valgrind-webrtc\webrtc_tests.bat --build-dir out --target Debug --test libjingle_p2p_unittest --tool drmemory_full
tools\valgrind-webrtc\webrtc_tests.bat --build-dir out --target Debug --test libjingle_peerconnection_unittest --tool drmemory_full
tools\valgrind-webrtc\webrtc_tests.bat --build-dir out --target Debug --test modules_unittests --tool drmemory_full

Review URL: https://webrtc-codereview.appspot.com/11819004

git-svn-id: http://webrtc.googlecode.com/svn/trunk@5888 4adac7df-926f-26a2-2b94-8c16560cd09d
 2014-04-11 14:16:27 +00:00
kjellander@webrtc.org
9f57404334 Excluding and suppressing Dr Memory test failures. 
With these tests excluded and failures suppressed
we should be able to bring Dr Memory Full into a
green state in
http://build.chromium.org/p/client.webrtc.fyi/waterfall
so we can move the bots into the main waterfall.

BUG=3158, 3159
TEST=Ran successful runs of the tests that never completed
using the reproduction steps in the issues listed above on
a local Windows box. The tests that just failed weren't tried,
since they cannot have been blocking other possibly failing
tests in the same binary.

R=pbos@webrtc.org
TBR=pbos

Review URL: https://webrtc-codereview.appspot.com/11209004

git-svn-id: http://webrtc.googlecode.com/svn/trunk@5850 4adac7df-926f-26a2-2b94-8c16560cd09d
 2014-04-07 08:01:06 +00:00