milksad
/
rust-bitcoin-unsafe-fast
14
0
Fork 0
Code Issues Pull Requests Activity
rust-bitcoin-unsafe-fast/.github/workflows/fuzz.yml

51 lines
1.8 KiB
YAML
Raw Normal View History

execute fuzzing in separate ci workflow
2021-09-23 08:36:07 +00:00
name: Fuzz
Revert "Temporarily disable fuzzing" This reverts commit 720ea29865c64e03a2b0c872e20e0dbf99cf305e.
2022-08-30 17:15:31 +00:00
on: [push, pull_request]
execute fuzzing in separate ci workflow
2021-09-23 08:36:07 +00:00
jobs:
fuzz:
feat: Support running CI locally with `act` Disable problematic jobs that involve Github Actions caching or `cross` whenever the environment is set to ACT. This allows running the CI pipeline locally and hopefully speeds up PR cycle times by reducing unexpected CI pipeline results.
2022-02-16 23:15:42 +00:00
if: ${{ !github.event.act }}
execute fuzzing in separate ci workflow
2021-09-23 08:36:07 +00:00
runs-on: ubuntu-20.04
strategy:
fail-fast: false
matrix:
Add Target and Difficulty types Currently we use the `Uint256` type to represent two proof of work integers, namely target and difficulty (work). It would be nice to not have a public integer type that is not fully implemented (i.e., does not implement arithmetic etc as do integer types in stdlib). Instead of implementing all the stdlib functions we can instead add two new wrapper types, since these are not general purpose integers they do not need to implement anything we do not need to use. - Add a `pow` module. - Put a modified version of `Uint256` to `pow`. - Add two new wrapper types `Target` and `Difficulty`. - Only implement methods that we use on each type. Note this patch does not remove the original `Uint256`, that will be done as a separate patch.
2022-08-16 05:07:59 +00:00
fuzz_target: [deser_net_msg, deserialize_address, deserialize_amount, deserialize_block, deserialize_psbt, deserialize_script, deserialize_transaction, deserialize_prefilled_transaction, deserialize_witness, outpoint_string, script_bytes_to_asm_fmt]
execute fuzzing in separate ci workflow
2021-09-23 08:36:07 +00:00
steps:
- name: Install test dependencies
run: sudo apt-get update -y && sudo apt-get install -y binutils-dev libunwind8-dev libcurl4-openssl-dev libelf-dev libdw-dev cmake gcc libiberty-dev
- uses: actions/checkout@v2
- uses: actions/cache@v2
id: cache-fuzz
with:
path: |
~/.cargo/bin
fuzz/target
target
key: cache-${{ matrix.target }}-${{ hashFiles('**/Cargo.toml','**/Cargo.lock') }}
- uses: actions-rs/toolchain@v1
with:
Tempararily pin fuzzer on rust 1.58 I think this might take a while to resolve and we should move ahead with 1.58. Looks like the fresh release of 1.59 added LLVM 13.0 that broke some things.
2022-02-25 07:45:49 +00:00
toolchain: 1.58
execute fuzzing in separate ci workflow
2021-09-23 08:36:07 +00:00
override: true
profile: minimal
- name: fuzz
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
run: cd bitcoin/fuzz && ./travis-fuzz.sh "${{ matrix.fuzz_target }}"
In fuzzing add a final job verifying all the fuzz targets have been executed
2021-09-24 08:47:16 +00:00
- run: echo "${{ matrix.fuzz_target }}.rs" >executed_${{ matrix.fuzz_target }}
- uses: actions/upload-artifact@v2
with:
name: executed_${{ matrix.fuzz_target }}
path: executed_${{ matrix.fuzz_target }}
verify-execution:
feat: Support running CI locally with `act` Disable problematic jobs that involve Github Actions caching or `cross` whenever the environment is set to ACT. This allows running the CI pipeline locally and hopefully speeds up PR cycle times by reducing unexpected CI pipeline results.
2022-02-16 23:15:42 +00:00
if: ${{ !github.event.act }}
In fuzzing add a final job verifying all the fuzz targets have been executed
2021-09-24 08:47:16 +00:00
needs: fuzz
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: actions/download-artifact@v2
- name: Display structure of downloaded files
run: ls -R
- run: find executed_* -type f -exec cat {} + | sort > executed
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
- run: ls bitcoin/fuzz/fuzz_targets | sort > expected
In fuzzing add a final job verifying all the fuzz targets have been executed
2021-09-24 08:47:16 +00:00
- run: diff expected executed