search

2753536587 / libyuv

Automatically exported from code.google.com/p/libyuv
0 stars 0 forks source link

unittests take too long to run #77

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
To integrate unittest execution into continuous testing, they need to run 
reasonably fast.  Currently they are prohibitive slow to run:

build\release\libyuv_unittest.exe --gtest_catch_exceptions=0 --gtest_filter=*

[       OK ] libyuvTest.ARGBScaleTo853 (14103 ms)
[----------] 210 tests from libyuvTest (793962 ms total)

[----------] Global test environment tear-down
[==========] 210 tests from 1 test case ran. (793967 ms total)
[  PASSED  ] 210 tests.
timex 794041.41ms

13.2 minutes

Original issue reported on code.google.com by fbarch...@google.com on 30 Aug 2012 at 6:59

GoogleCodeExporter commented 9 years ago 
r336 sets iterations to 1 reducing unittests to 22 seconds.

Windows
build\release\libyuv_unittest.exe --gtest_catch_exceptions=0 --gtest_filter=*
[----------] Global test environment tear-down
[==========] 210 tests from 1 test case ran. (22306 ms total)
[  PASSED  ] 210 tests.
timex 22415.03ms

Linux
[----------] Global test environment tear-down
[==========] 210 tests from 1 test case ran. (11075 ms total)
[  PASSED  ] 210 tests.

Linux
real    0m11.086s
user    0m10.850s
sys     0m0.210s

[----------] Global test environment tear-down
[==========] 210 tests from 1 test case ran. (11290 ms total)
[  PASSED  ] 210 tests.

Mac
real    0m11.311s
user    0m10.466s
sys     0m0.835s
5.8 seconds to build unittests on windows and mac.  2.9 seconds on linux

Original comment by fbarch...@chromium.org on 30 Aug 2012 at 9:24