CI: Use matrix.runtime.uri
for try-runtime
tests
#530
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.
Some tests gated with the
try-runtime
feature have the ability to configure the node URI using some hard-coded defaults, e.g.:Additionally, we have a dedicated runtime
uri
specified in theruntimes-matrix.json
, e.g.,so, let's use those dedicated
uri
s instead of the hard-coded ones.I came across this issue by accident when Kusama's
remote_tests::next_inflation
failed withError while getting storage data
here: https://github.com/polkadot-fellows/runtimes/actions/runs/12526255825/job/34938624858?pr=519.I wasn't sure if it is flaky, missing some keys in the actual block, or just a connection problem, so I also enabled
remote-ext=info
logs (if the logs are too much, we can switch toremote-ext=warn/error
).