-
Notifications
You must be signed in to change notification settings - Fork 593
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
IceGrid/activation test fixes #3452
Conversation
} | ||
catch (const Ice::NoEndpointException&) | ||
{ | ||
this_thread::sleep_for(chrono::milliseconds(500)); | ||
continue; | ||
} | ||
} | ||
test(admin->isServerEnabled("server2")); | ||
waitForServerState(admin, "server2", IceGrid::ServerState::Active); |
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.
With the previous code, we can exit the loop after getting NoEndpointException if the server just get enabled before we send the next ice_ping
request.
In this situation waitForServerState
would hang as there is no request activating the server.
} | ||
} | ||
test(admin->isServerEnabled("server2")); | ||
waitForServerState(admin, "server2", IceGrid::ServerState::Active); | ||
obj->ice_ping(); |
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.
This ice_ping
request after the server is already activate and before is stopped doesn't make sense. Maybe it was mean to be done before the waitForServerState
.
} | ||
catch (const Ice::NoEndpointException&) | ||
{ | ||
this_thread::sleep_for(chrono::milliseconds(500)); | ||
continue; |
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.
Is this continue necessary?
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.
No. we can remove it.
Fix #3447