From my understanding this is only used by `chiavdf` source builds which
happen only if `install-timelord.sh` gets called but it doesn't in the
addressed cases.
* Force apt to install the things we asked it to
* Update .github/workflows/benchmarks.yml
Co-authored-by: dustinface <35775977+xdustinface@users.noreply.github.com>
Co-authored-by: dustinface <35775977+xdustinface@users.noreply.github.com>
* Start fast full node tests
* Perf improvement on send_transaction
* Major performance improvement for mempool test
* Speed up another test
* Speed up mempool tests startup
* Lint
* Debug tests
* Try function scope for wallet_nodes
* Update comment
* MacOS isn't updating OpenSSL in install.sh
* Exit if no brew on MacOS
* Code the if tree like a pro instead.
Co-authored-by: Kyle Altendorf <sda@fstab.net>
Co-authored-by: Kyle Altendorf <sda@fstab.net>
* Check for vulnerable openssl
* Update OpenSSL on MacOS
* First attempt - openssl Ubuntu 18.04 and 20.04
* place local/bin ahead in PATH
* specify install openssl
* correct path
* run ldconfig
* stop building and check for patched openssl
* spell sudo right by removing it
* Remove openssl building - 1st attempt RHs
* Test Windows OpenSSL version HT @AmineKhaldi
* when going through a reorg, maintain all chain state until the very end, when the new fork has been fully validated and added
* when rolling back the chain, also rollback the height-to-hash map
* add tests
* improve error message when a block is missing from the blockchain database
* Update chia/full_node/block_height_map.py
Co-authored-by: Kyle Altendorf <sda@fstab.net>
Co-authored-by: Kyle Altendorf <sda@fstab.net>
* Rename confusing fixtures, especially ones with the same name but different implementation
* revert premature fixture rename: two_wallet_nodes_start_height_1
* Consolidate test fixtures
* Truncate CAT asset_id output to 32 bytes. A wallet RPC change is needed
to properly separate out the asset ID from the TAIL program returned by
`get_all_wallet_info_entries()`
* Move the truncation to the assignment location
* Bump actions/github-script from 4 to 6
Bumps [actions/github-script](https://github.com/actions/github-script) from 4 to 6.
- [Release notes](https://github.com/actions/github-script/releases)
- [Commits](https://github.com/actions/github-script/compare/v4...v6)
---
updated-dependencies:
- dependency-name: actions/github-script
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
* Update to github.rest.* for calls to API for compat w/ github-script@v5+
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Chris Marslender <chrismarslender@gmail.com>
https://github.com/pallets/click/issues/2225
Doing this instead of updating since updating black will change several
files due to some formatting change. I would like to take that on
separately from unbreaking CI.
* Add coverage (without collection)
* Separate test_block_compression() to avoid coverage-related hangs
* Revert "Separate test_block_compression() to avoid coverage-related hangs"
This reverts commit ebad3d0017.
* multiprocessing.set_start_method("spawn")
* multiprocessing.set_start_method() in conftest.py
* hand hold cc wallet tests
* lint
* spawn for running chia as well
* handle already set start method case
* a bit more timeout for test_multiple_writers
* more timeout for test_writer_lock_blocked_by_readers
* 45 minute tieout for tests/pools/
* 45 minute tieout for tests/pools/
* some more hand holding sleeps
* report coverage in each workflow
only really useful to make sure it is capturing something
* oops
* complete the job name and the JOB_NAME
* better coverage result file names
* reset worker process titles
* rebuild workflows
* rebuild workflows
* black
* black
* rebuild workflows
* push timeouts
* actually include the updated workflows...
* push more workflow timeouts
* parallel=True
* rebuild workflows