lbrycrd/.travis
MarcoFalke 73a8408bc3
Merge #14092: tests: Dry run bench_bitcoin as part "make check" to allow for quick identification of assertion/sanitizer failures in benchmarking code
dfef0df840 tests: Dry run bench_bitcoin (-evals=1 -scaling=0: <1 second running time) as part "make check" to allow for quick identification of assertion/sanitizer failures in benchmarking code (practicalswift)
00c6306a61 Remove RUN_BENCH logic (practicalswift)

Pull request description:

  Dry run `bench_bitcoin` (`-evals=1 -scaling=0`: <1 second running time) as part `make check` to allow for quick identification of assertion/sanitizer failures or crashes in benchmarking code.

  This is already tested in Travis but it is nice to have it locally too. The cost is near zero.

Tree-SHA512: 1f51b86b34bf97f75785f2694891d80f1bfb3e050211e6f6c35d8d9bc80c75bdebaa5ebfa51855ac0cf76d8773c3026bc576f60d0227afb0e646d728b83abde7
2018-11-05 09:31:01 -05:00
..
lint_04_install.sh build: Pin to specific versions of Python packages we install from PyPI in Travis 2018-10-16 13:48:16 +02:00
lint_05_before_script.sh move remaining travis build steps into individual files 2018-08-27 12:23:25 +02:00
lint_06_script.sh move remaining travis build steps into individual files 2018-08-27 12:23:25 +02:00
README.md number .travis/ script according to build lifecycle and add README to explain 2018-08-27 12:23:25 +02:00
test_03_before_install.sh use export LC_ALL=C.UTF-8 2018-08-27 12:23:25 +02:00
test_04_install.sh use export LC_ALL=C.UTF-8 2018-08-27 12:23:25 +02:00
test_05_before_script.sh use export LC_ALL=C.UTF-8 2018-08-27 12:23:25 +02:00
test_06_script.sh Merge #14092: tests: Dry run bench_bitcoin as part "make check" to allow for quick identification of assertion/sanitizer failures in benchmarking code 2018-11-05 09:31:01 -05:00

travis build scripts

The .travis directory contains scripts for each build step in each build stage. Currently the travis build defines two stages lint and test. Each stage has it's own lifecycle. Every script in here is named and numbered according to which stage and lifecycle step it belongs to.