HomePhabricator

[SECP256K1] make test count iteration configurable by environment variable

Description

[SECP256K1] make test count iteration configurable by environment variable

Summary:

You can set the test iteration count by command-line parameter but it is
very hard to control the iteration count used by make check and even
harder to control the count when this is run through Bitcoin Core's
build system. Using an environment var solves both problems.

Backport of secp256k1#851

Test Plan:

SECP256K1_TEST_ITERS=16 ninja check-secp256k1

Should succeed but:

SECP256K1_TEST_ITERS=0 ninja check-secp256k1

Should fail with error An iteration count of 0 or less is not allowed.

Reviewers: #bitcoin_abc, PiRK

Reviewed By: #bitcoin_abc, PiRK

Differential Revision: https://reviews.bitcoinabc.org/D9375

Details

Provenance
Andrew Poelstra <apoelstra@wpsoftware.net>Authored on Nov 23 2020, 01:05
FabienCommitted on Apr 8 2021, 13:11
FabienPushed on Apr 8 2021, 13:14
Reviewer
Restricted Project
Differential Revision
D9375: [SECP256K1] make test count iteration configurable by environment variable
Parents
rABC543f9c584f75: [SECP256K1] Don't use reserved identifiers memczero and benchmark_verify_t
Branches
Unknown
Tags
Unknown