Run benchmark tests "logic only" on Travis CI

The benchmark tests are run only once without reports.

Besides using the command line option --benchmark-disable to run the tests only once, a custom marker is used to select only one parameter value or tuple (a pytest param object) for test functions that are parameterized. The marker is named skip_bench for now :smile:. Here's an example of how this works:

@mark.parametrize(
    "t, k",
    [
        param(1, 5, marks=mark.skip_bench),
        (3, 5),
        (5, 5),
        # ...
    ],
)
def test_benchmark_hbavss_lite_dealer(test_router, benchmark, t, k): 
    # ...

The above test can then be run in three different ways:

pytest -m skip_bench ... - only tests that are marked with skip_bench will be run;
pytest -m "no skip_bench" ... - tests that are marked with skip_bench will be skipped, and
pytest ... - (no marker is used) all tests will be run.

When the goal is to benchmark all, there's no need to know about this marker, and option 3 above will do. The main purpose is really for cases such as on Travis CI, in which one wishes to quickly check whether the tests run for a "subsample" of the parameters. Option 2, is not really useful, and is just a consequence of how the marker mechanism works.

If someone has a better idea for the name of the marker please say as I don't particularly like the name!

See the benchmark/README.md for more explanations.

Tiny issues were also fixed:

use_fft was replaced with use_omega_powers in test_benchmark_reed_solomon.py
in order to use the setup= keyword argument benchmark.pedantic() is used instead of benchmark() in tests/fixtures.py

initc3 / HoneyBadgerMPC

Run benchmark tests "logic only" on Travis CI #451

Codecov Report