hanahmily commented on a change in pull request #64:
URL:
https://github.com/apache/skywalking-infra-e2e/pull/64#discussion_r741582592
##########
File path: docs/en/setup/Configuration-File.md
##########
@@ -150,6 +152,12 @@ trigger:
The Trigger executed successfully at least once, after success, the next stage
could be continued. Otherwise, there is an error and exit.
+If you get the following error message when using the trigger, You should
check whether the port is useful. A possible reason may be that the exporting
service needs time to set up, so you can add a larger interval to avoid the
error.
Review comment:
Does the e2e framework support `NodePort` or `LoadBalancer`? They are
the more canonical ways to expose services than `port-forward`.
##########
File path: docs/en/setup/Configuration-File.md
##########
@@ -150,6 +152,12 @@ trigger:
The Trigger executed successfully at least once, after success, the next stage
could be continued. Otherwise, there is an error and exit.
+If you get the following error message when using the trigger, You should
check whether the port is useful. A possible reason may be that the exporting
service needs time to set up, so you can add a larger interval to avoid the
error.
Review comment:
@kezhenxu94 How does the `swctl` connect to UI in current e2e cases?
##########
File path: docs/en/setup/Configuration-File.md
##########
@@ -150,6 +152,12 @@ trigger:
The Trigger executed successfully at least once, after success, the next stage
could be continued. Otherwise, there is an error and exit.
+If you get the following error message when using the trigger, You should
check whether the port is useful. A possible reason may be that the exporting
service needs time to set up, so you can add a larger interval to avoid the
error.
Review comment:
Thanks @zhenxu
And FWIK, the item is not special to the e2e framework. The user should
ensure a service accessible before accessing it. It's common sense more than a
FAQ which the e2e user should care about.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]