solana/ci/test-bench.sh

#!/bin/bash -e

cd "$(dirname "$0")/.."

ci/version-check.sh nightly
export RUST_BACKTRACE=1

_() {
  echo "--- $*"
  "$@"
}

_ cargo bench --features=unstable --verbose
move bench to a seprate, parallel step 2018-08-13 15:57:23 -07:00			`#!/bin/bash -e`

			`cd "$(dirname "$0")/.."`

Boot criterion (#1032) * Revert benchmarks back to libtest Criterion has too many dependencies, it's execution as slower, and we didn't see the kind of precision we had hoped for to use it to block CI builds. * Ignore benchmarks that take more than a few milliseconds per iteration * Revert "Ignore benchmarks that take more than a few milliseconds per iteration" This reverts commit b87cdf6ef4a2549ec09e282014391de695473699. * Don't run benchmarks in CI They are already built in the nightly build. Executing them in CI doesn't add much value until the results are precise enough to act on. 2018-08-22 07:57:07 -07:00			`ci/version-check.sh nightly`
move bench to a seprate, parallel step 2018-08-13 15:57:23 -07:00			`export RUST_BACKTRACE=1`

			`_() {`
			`echo "--- $*"`
			`"$@"`
			`}`

Boot criterion (#1032) * Revert benchmarks back to libtest Criterion has too many dependencies, it's execution as slower, and we didn't see the kind of precision we had hoped for to use it to block CI builds. * Ignore benchmarks that take more than a few milliseconds per iteration * Revert "Ignore benchmarks that take more than a few milliseconds per iteration" This reverts commit b87cdf6ef4a2549ec09e282014391de695473699. * Don't run benchmarks in CI They are already built in the nightly build. Executing them in CI doesn't add much value until the results are precise enough to act on. 2018-08-22 07:57:07 -07:00			`_ cargo bench --features=unstable --verbose`