Skip to content

Conversation

jcantrill
Copy link
Contributor

No description provided.

@jcantrill
Copy link
Contributor Author

[test]

@openshift-bot
Copy link
Contributor

Java Client Test Results: SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test-openshift-restclient-java/25/)

@jcantrill
Copy link
Contributor Author

[merge]

@openshift-bot
Copy link
Contributor

Java Client Merge Results: SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge-openshift-restclient-java/8/)

@openshift-bot
Copy link
Contributor

Evaluated for javaclient up to 078af7c

openshift-bot pushed a commit that referenced this pull request Jul 26, 2015
@openshift-bot openshift-bot merged commit fa6c55d into openshift:master Jul 26, 2015
@jcantrill jcantrill deleted the 197_add_port_forward_delay branch July 26, 2015 22:18
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jcantrill I seriously doubt that a fixed timeout is the right thing to do. What if trying to launch the process takes longer than the hard coded 1 sec?
IMHO you should have a shared lock which makes sure that testing for the process to be alive only occurrs once the process is launched.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants