1
88%
master: 92%

Ran 19 Aug 2018 12:17PM UTC

Files 36

Run time 3s

Badge

Embed ▾

Committed 19 Aug 2018 12:06PM UTC coverage: 87.629% (+0.8%) from 86.877%

Job # COMPILER=g++ C_COMPILER=gcc BUILD_TYPE=Coverage

Build Type

Pull #657

travis-ci

Committed by

web-flow

Commit Message

Counter(): add 'one thousand' param.

Needed for https://github.com/google/benchmark/pull/654

Custom user counters are quite custom. It is not guaranteed
that the user *always* expects for these to have 1k == 1000.
If the counter represents bytes/memory/etc, 1k should be 1024.

Some bikeshedding points:
1. Is this sufficient, or do we really want to go full on
   into custom types with names?
   I think just the '1000' is sufficient for now.
2. Should there be a helper benchmark::Counter::Counter{1000,1024}()
   static 'constructor' functions, since these two, by far,
   will be the most used?
3. In the future, we should be somehow encoding this info into JSON.

Pull Request Pull Request #657: Counter(): add 'one thousand' param.

Run Details

1530 of 1746 relevant lines covered (87.63%)

5019604.16 hits per line

google / benchmark / 1737 / 1
88%
master: 92%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1737.1 (COMPILER=g++ C_COMPILER=gcc BUILD_TYPE=Coverage)

google / benchmark / 1737 / 1 88% master: 92%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1737.1 (COMPILER=g++ C_COMPILER=gcc BUILD_TYPE=Coverage)

google / benchmark / 1737 / 1
88%
master: 92%

README BADGES
x