* 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
* asyncio.get_event_loop() is deprecated in 3.10, stop using it
https://docs.python.org/3.10/library/asyncio-eventloop.html#asyncio.get_event_loop
> Deprecated since version 3.10: Deprecation warning is emitted if there is no running event loop. In future Python releases, this function will be an alias of get_running_loop().
* black
* attempt to checkout test-cache directly to desired location
* rebuild workflows
* maybe we can use CHIA_ROOT
* use CHIA_ROOT to find blocks and plots for tests
* oops
* more informational printing
* oops
* --capture no for debugging
* flake8
* import os
* undo some unrelated changes now covered elsewhere
* undo some debug changes
* rebuild workflows
* minor lock scope reduction
* use the lock in tests
* Use the passed root_path in configure CLI command
* switch to lock_and_load_config()
* oops
* cleanup
* make _load_config_maybe_locked() private
* black
* Remove future improvement opportunity TODO comment
* add inline executor and an option to run single-threaded
* add option to run test_full_sync in single-thread mode, to include block validation in profiles. Also attempt to speed it up by disabling db_sync
* fixup and enable tests for the edge cases of absolute timestamp and absolute height conditions in mempool_manager
* Update chia/full_node/full_node_api.py
Co-authored-by: Adam Kelly <338792+aqk@users.noreply.github.com>
Co-authored-by: Adam Kelly <338792+aqk@users.noreply.github.com>
* fix typo in wallet_puzzle_store
* check some SQL statements
* deduplicate name SQL index
* deduplicate wallet_type index
* deduplicate wallet_id index
* Hardcoded SSL test certs/keys
* Added a second set of certs/keys.
Cert/key sets are infinitely cycled-through using get_next_private_ca_cert_and_key() and get_next_nodes_certs_and_keys()
* More cert/key sets and a tool to generate them
* Updated SSL generator to sign with the appropriate root CA.
Fixed linter issues.
* Linter fixes
* Updated generate_ssl_for_nodes() based on feedback
* disable the pytest-monitor plugin if not reporting results
pytest-monitor uses multiprocessing and has caused multiple confusing
issues. Perhaps it can be adjusted to not use multiprocessing, but
for now lets just isolate the oddities to where we actually use it.
* use a template for resource usage check, similar to timelord install
* hint testconfig.custom_vars
* Rename confusing fixtures, especially ones with the same name but different implementation
* rename test_environment to test_plot_environment
* Make it so setup_two_nodes is no longer the name of a fixture and a utility function
* revert premature fixture rename: two_wallet_nodes_start_height_1
