NONEVM-1954: support multiple ton networks #1862
Merged
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.
This PR enables multiple concurrent TON network instances for parallel testing
Primary Changes
Testing Support
Others
Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.
Why
The changes introduce a new parallel testing setup for TON, enhance the blockchain component to support dynamic port allocation for TON services, and ensure that the TON blockchain component is properly configured for testing environments. These changes aim to improve the flexibility and robustness of testing different configurations and scenarios within the TON blockchain network, specifically addressing the need for parallel execution and dynamic networking.
What
TestTonParallel
with its respective TOML fileparallel_ton.toml
and timeout setting.CommonDBVars
tocommonDBVars
).generateUniquePortsFromBase
to create a unique set of ports for each TON service based on a given base port.network
package fromtestcontainers-go
.port
configuration for the TON blockchain instance, ensuring consistency with the new dynamic port allocation approach.