-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Reduce the chances that successfulCheckTest will fail #14688
Conversation
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
Signed-off-by: Sergii Kabashniuk <skabashniuk@redhat.com>
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
Signed-off-by: Sergii Kabashniuk <skabashniuk@redhat.com>
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
ci-test |
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
@eclipse/eclipse-che-qa can you review test results? |
@skabashnyuk: there is expected failure in Java selenium tests results here. No regression is found. |
What does this PR do?
The cause of the fail is that TestServerChecker has only 500msec to do the job correctly in successfulCheckTest. Since successfulCheckTest is the single testcase that used TestServerChecker constructed in setUp it may occasionally fail if the time between setUp and successfulCheckTest.checker.start(); are longer then 500msec
What issues does this PR fix or reference?
#13211
Release Notes
n/a
Docs PR
n/a