interop: test-plans ping (TLS, WSS, JSON output)#1301
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Extends
interop/transport/ping_test.pyfor the libp2p/test-plans transport-interop harness:--test-plansmode with uppercase env vars, JSON dialer output,listenerAddrRedis coordination, TLS and WSS paths, grace periods and retries appropriate for cross-implementation runs.Updates
interop/README.mdto clarify how test-plans builds the Python image versus unified-testing and where the canonical script lives.Fixes #1300
Testing
make testmake docstest-plansfor all transport tests except forchromium-rust-v0.53 x python-v0.x (ws, noise, mplex)(the chromium-rust has known issues)