Check cost model update and hard fork to PV10 in upgrade testing #2738
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Added a new test `test_update_cost_models` to verify the update of PlutusV3 cost models. - Introduced a new JSON file `cost_models_pv10.json` containing the cost models for PlutusV3. - Updated the `node_upgrade_pytest.sh` script to include the new test for updating cost models. - Added necessary imports and constants in `test_node_upgrade.py`.
- Added a new test `test_hardfork` to `test_node_upgrade.py` to handle the hard fork to protocol version 10. - Updated `node_upgrade_pytest.sh` to include the new hard fork test step. - Ensured the test runs only on step 3 of upgrade testing.
Updated the BASE_TAR_URL in the env_nightly_upgrade file to point to the latest release version 10.1.2. This ensures that the nightly upgrade process uses the most recent released version of the cardano-node.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.