Skip to content
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

Flaky test: TestRunStdinPipe #21365

Closed
thaJeztah opened this issue Mar 21, 2016 · 3 comments
Closed

Flaky test: TestRunStdinPipe #21365

thaJeztah opened this issue Mar 21, 2016 · 3 comments
Labels
area/testing priority/P1 Important: P1 issues are a top priority and a must-have for the next release.
Milestone

Comments

@thaJeztah
Copy link
Member

Flaky test on gccgo, or actual error? https://jenkins.dockerproject.org/job/Docker-PRs-gccgo/3540/console. Seen failing on #21354

01:19:42 PASS: docker_cli_run_test.go:3905: TestRunStdinBlockedAfterContainerExit.pN52_github_com_docker_docker_integration_cli.DockerSuite 1.469s
01:19:45 
01:19:45 ----------------------------------------------------------------------
01:19:45 FAIL: docker_cli_run_test.go:88: TestRunStdinPipe.pN52_github_com_docker_docker_integration_cli.DockerSuite
01:19:45 
01:19:45 docker_cli_run_test.go:105:
01:19:45     c.Errorf("logs didn't print the container's logs %s", containerLogs)
01:19:45 ... Error: logs didn't print the container's logs 
01:19:45 
01:19:46 
01:19:46 ----------------------------------------------------------------------
@thaJeztah
Copy link
Member Author

Also just seen on experimental, so not a gccgo only issue

@icecrime
Copy link
Contributor

This will be fixed by the next containerd vendoring (cc @tonistiigi).

@icecrime icecrime added this to the 1.11.0 milestone Mar 23, 2016
@icecrime icecrime added the priority/P1 Important: P1 issues are a top priority and a must-have for the next release. label Mar 23, 2016
@icecrime icecrime changed the title Flaky test: TestRunStdinPipe (gccgo) Flaky test: TestRunStdinPipe Mar 24, 2016
@icecrime
Copy link
Contributor

I believe this is closed by #21457.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing priority/P1 Important: P1 issues are a top priority and a must-have for the next release.
Projects
None yet
Development

No branches or pull requests

2 participants