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.

Sign up for GitHub

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

Jump to bottom

crictl e2e test is failing. #539

Closed
Random-Liu opened this issue Sep 19, 2019 · 1 comment · Fixed by #545
Closed

crictl e2e test is failing. #539

Random-Liu opened this issue Sep 19, 2019 · 1 comment · Fixed by #545
Assignees
@saschagrunert
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test.

Comments

@Random-Liu
Copy link
Contributor

It is currently blocking PRs.

Summarizing 8 Failures:
[Fail] crictl: pull [It] should succeed without tag or digest 
/home/travis/gopath/src/github.com/kubernetes-sigs/cri-tools/test/framework/framework.go:104
[Fail] crictl: pull [It] should succeed with tag 
/home/travis/gopath/src/github.com/kubernetes-sigs/cri-tools/test/framework/framework.go:104
[Fail] crictl: pull [It] should fail on not existing image 
/home/travis/gopath/src/github.com/kubernetes-sigs/cri-tools/test/framework/framework.go:126
[Fail] crictl: info [It] should succeed 
/home/travis/gopath/src/github.com/kubernetes-sigs/cri-tools/test/framework/framework.go:104
[Fail] crictl: info [AfterEach] should fail with additional argument 
/home/travis/gopath/src/github.com/kubernetes-sigs/cri-tools/test/framework/framework.go:205
[Fail] crictl: pull [It] should succeed with digest 
/home/travis/gopath/src/github.com/kubernetes-sigs/cri-tools/test/framework/framework.go:104
[Fail] crictl: pull [AfterEach] should succeed to show the help 
/home/travis/gopath/src/github.com/kubernetes-sigs/cri-tools/test/framework/framework.go:205
[Fail] crictl: version [It] should succeed 
/home/travis/gopath/src/github.com/kubernetes-sigs/cri-tools/test/framework/framework.go:104
Ran 12 of 12 Specs in 246.295 seconds
FAIL! -- 4 Passed | 8 Failed | 0 Pending | 0 Skipped
Ginkgo ran 1 suite in 4m18.491441555s
Test Suite Failed
Makefile:108: recipe for target 'test-e2e' failed
make: *** [test-e2e] Error 1
@Random-Liu Random-Liu added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label Sep 19, 2019
@saschagrunert
Copy link
Member

The issue is that we moved conmon out of the repository. I will fix this and propose a PR.

@saschagrunert saschagrunert mentioned this issue Sep 20, 2019
Closed
@saschagrunert saschagrunert mentioned this issue Oct 2, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@saschagrunert saschagrunert

Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test.
Projects
None yet
Milestone
No milestone
2 participants
@saschagrunert @Random-Liu