Skip to content
This repository was archived by the owner on Jun 28, 2024. It is now read-only.

integration/docker: add test to check yamux IO keep alive#311

Merged
chavafg merged 1 commit intokata-containers:masterfrom
devimc:yamux/keepaliveTest
May 18, 2018
Merged

integration/docker: add test to check yamux IO keep alive#311
chavafg merged 1 commit intokata-containers:masterfrom
devimc:yamux/keepaliveTest

Conversation

@devimc
Copy link
Copy Markdown

@devimc devimc commented May 17, 2018

Check that yamux connection write timeout never occurs.
Connection write timeout occurs only if yamux default
configuration is used to create the client.

Depends-on: github.com/kata-containers/proxy#71

fixes #310

Signed-off-by: Julio Montes julio.montes@intel.com

Expect(0).To(Equal(exitCode))
_, _, exitCode = dockerPause(id)
Expect(0).To(Equal(exitCode))
time.Sleep(45 * time.Second)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

could you explain why 45 sec is needed and added it a comment if needed?

@devimc devimc force-pushed the yamux/keepaliveTest branch from 80a12f3 to ec334e0 Compare May 17, 2018 19:01
@devimc
Copy link
Copy Markdown
Author

devimc commented May 17, 2018

@jcvenegas changes applied, thanks

@devimc devimc force-pushed the yamux/keepaliveTest branch from ec334e0 to f77551f Compare May 17, 2018 19:06
@jcvenegas
Copy link
Copy Markdown
Member

@chavafg ptal.

@devimc
Copy link
Copy Markdown
Author

devimc commented May 17, 2018

waiting for kata-containers/proxy#71

@chavafg
Copy link
Copy Markdown
Contributor

chavafg commented May 17, 2018

lgtm

Approved with PullApprove

Copy link
Copy Markdown

@sboeuf sboeuf left a comment

Choose a reason for hiding this comment

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

You should mention in the commit message that this test is based on the default configuration. Otherwise the commit message is bit confusing.

Check that yamux connection write timeout never occurs.
Connection write timeout occurs only if yamux default
configuration is used to create the client.

Depends-on: github.com/kata-containers/proxy#71

fixes kata-containers#310

Signed-off-by: Julio Montes <julio.montes@intel.com>
@devimc devimc force-pushed the yamux/keepaliveTest branch from f77551f to 4c37c7a Compare May 17, 2018 21:20
@devimc
Copy link
Copy Markdown
Author

devimc commented May 17, 2018

@sboeuf done, thanks

Copy link
Copy Markdown

@jodh-intel jodh-intel left a comment

Choose a reason for hiding this comment

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

lgtm

})
})

// To get more info about this test, see https://github.com/kata-containers/agent/issues/231
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Good use of comments!

@chavafg chavafg merged commit 0206dd4 into kata-containers:master May 18, 2018
@devimc devimc deleted the yamux/keepaliveTest branch May 28, 2018 18:44
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add test for yamux: keepalive failed: i/o deadline reached

5 participants