mirror of
https://github.com/google/benchmark.git
synced 2024-12-27 13:00:36 +08:00
32a1e39720
* Update AUTHORS and CONTRIBUTORS * Fix WSL self-test failures Some of the benchmark self-tests expect and check for a particular output format from the benchmark library. The numerical values must not be infinity or not-a-number, or the test will report an error. Some of the values are computed bytes-per-second or items-per-second values, so these require that the measured CPU time for the test to be non-zero. But the loop that is being measured was empty, so the measured CPU time for the loop was extremely small. On systems like Windows Subsystem for Linux (WSL) the timer doesn't have enough resolution to measure this, so the measured CPU time was zero. This fix just makes sure that these tests have something within the timing loop, so that the benchmark library will not decide that the loop takes zero CPU time. This makes these tests more robust, and in particular makes them pass on WSL. |
||
---|---|---|
.. | ||
AssemblyTests.cmake | ||
basic_test.cc | ||
benchmark_gtest.cc | ||
benchmark_name_gtest.cc | ||
benchmark_test.cc | ||
BUILD | ||
clobber_memory_assembly_test.cc | ||
CMakeLists.txt | ||
commandlineflags_gtest.cc | ||
complexity_test.cc | ||
cxx03_test.cc | ||
diagnostics_test.cc | ||
display_aggregates_only_test.cc | ||
donotoptimize_assembly_test.cc | ||
donotoptimize_test.cc | ||
filter_test.cc | ||
fixture_test.cc | ||
internal_threading_test.cc | ||
link_main_test.cc | ||
map_test.cc | ||
memory_manager_test.cc | ||
multiple_ranges_test.cc | ||
options_test.cc | ||
output_test_helper.cc | ||
output_test.h | ||
register_benchmark_test.cc | ||
report_aggregates_only_test.cc | ||
reporter_output_test.cc | ||
skip_with_error_test.cc | ||
state_assembly_test.cc | ||
statistics_gtest.cc | ||
string_util_gtest.cc | ||
templated_fixture_test.cc | ||
user_counters_tabular_test.cc | ||
user_counters_test.cc | ||
user_counters_thousands_test.cc |