-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[e2e] Make probe outputs more informative #5140
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding this. LGTM. One nit.
faef0de
to
18fc1cb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, when the failure of testACNPNodePortServiceSupport
is fixed.
I think other failed cases are not introduced by this commit?
"agnhost connect" outputs nothing when it succeeds. The current probe output like below can't tell which attemp succeeded and if it really succeeded: ``` TIMEOUT TIMEOUT ``` We output "CONNECTED" when a connection succeeds and prepend a sequence number for each attempt, to make the result more informative. An example output: ``` 1: CONNECTED 2: TIMEOUT 3: TIMEOUT ``` Signed-off-by: Quan Tian <[email protected]>
The failure has been fixed |
/skip-all |
"agnhost connect" outputs nothing when it succeeds. The current probe output like below can't tell which attemp succeeded and if it really succeeded:
We output "CONNECTED" when a connection succeeds and prepend a sequence number for each attempt, to make the result more informative. An example output:
For #5139