rust-bitcoin-unsafe-fast/contrib/test.sh

#!/bin/sh

set -ex

CRATES="bitcoin hashes"

for crate in ${CRATES}
do
    (
        cd "$crate"
        ./contrib/test.sh
    )
done

exit 0
ci: Use set -ex instead of /bin/sh -ex Setting `-ex` in the shebang makes it a little hard to see since folks are used to glancing up and looking for `set -ex`. Both styles achieve the same result, so this does not change the logic of the script. 2022-07-21 22:06:51 +00:00			`#!/bin/sh`

			`set -ex`
Extract travis testing into locally-runnable script 2019-01-24 16:37:55 +00:00
Import bitcoin_hashes crate into hashes We would like to bring the `bitcoin_hashes` crate into the `rust-bitcoin` repository. Import `bitcoin_hashes` into `rust-bitocin/hashes`, doing so looses all the commit history from the original crate but if we archive the original repository then the history will be preserved. We maintain the same version number obviously and in the changelog we note the change of repository. Commit hash that was tip of `bitcoin_hashes` at time of import: commit 54c16249e06cc6b7870c7fc07d90f489d82647c7 Includes making `embedded` and `fuzzing` per-crate i.e., move them into `bitcoin` as hashes includes these also. NOTE: Does _not_ enable fuzzing for `hashes` in CI. Notes on CI: Attempts to merge in the github actions from the hashes crate however reduces coverage by not running hashes tests for beta toolchain. Some additional work could be done to improve the CI to increase efficiency without reducing coverage. Leaving for another day. 2022-09-16 01:52:57 +00:00			`CRATES="bitcoin hashes"`
no_std support Based on the original work by Justin Moon. MSRV unchanged from 1.29.0. When `std` is off, `no-std` must be on, and we use the [`alloc`](https://doc.rust-lang.org/alloc/) and core2 crates. The `alloc` crate requires the user define a global allocator. * Import from `core` and `alloc` instead of `std` * `alloc` only used if `no-std` is on * Create `std` feature * Create `no-std` feature which adds a core2 dependency to polyfill `std::io` features. This is an experimental feature and should be used with caution. * CI runs tests `no-std` * MSRV for `no-std` is 1.51 or so 2021-06-09 10:34:44 +00:00
Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script 2022-09-07 23:32:08 +00:00			`for crate in ${CRATES}`
Extract travis testing into locally-runnable script 2019-01-24 16:37:55 +00:00			`do`
			`(`
Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script 2022-09-07 23:32:08 +00:00			`cd "$crate"`
			`./contrib/test.sh`
Extract travis testing into locally-runnable script 2019-01-24 16:37:55 +00:00			`)`
Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script 2022-09-07 23:32:08 +00:00			`done`
update Travis and README for manual rustc 1.22.0 steps 2020-09-10 17:55:47 +00:00
Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script 2022-09-07 23:32:08 +00:00			`exit 0`