cardano-testnet: call the CLI check-node-configuration to catch configuration errors #6096
+4
−0
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.
Description
Call the CLI's "new" check-node-configuration command in
cardano-testnet
setup.This both serves as a test of
check-node-configuration
and will also help catch configuration errors earlier (and with a nice error message). The latter is particularly important as we will soon releasecardano-testnet
and let users supply genesis files (see roadmap and issue about supplying genesis files).Fixes #6028
How to trust this PR
The tests still pass, so the cal is successful
Try to break the genesis files, for example apply this patch:
Run
cardano-testnet
's tests:cabal test cardano-testnet-test
And observe that, as expected, the tests fail with the expected error:
Checklist
hlint
. See.github/workflows/check-hlint.yml
to get thehlint
versionstylish-haskell
. See.github/workflows/stylish-haskell.yml
to get thestylish-haskell
version