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

Go 1.10: x509_test.go:700: server cert: Expected error, got none #34

Closed
nim-nim opened this issue Mar 26, 2018 · 3 comments
Closed

Go 1.10: x509_test.go:700: server cert: Expected error, got none #34

nim-nim opened this issue Mar 26, 2018 · 3 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@nim-nim
Copy link

nim-nim commented Mar 26, 2018

1.9.6 does not pass unit tests with Go 1.10. At least:

+ GOPATH=/builddir/build/BUILD/apiserver-kubernetes-1.9.6/_build:/usr/share/gocode
+ go test -buildmode pie -compiler gc -ldflags '-extldflags '\''-Wl,-z,relro  -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld '\'''
--- FAIL: TestX509 (0.02s)
	x509_test.go:700: server cert: Expected error, got none
--- FAIL: TestX509Verifier (0.00s)
	x509_test.go:855: server cert disallowed: Expected error, got none
FAIL
exit status 1
FAIL	k8s.io/apiserver/pkg/authentication/request/x509	0.040s

+ GOPATH=/builddir/build/BUILD/apiserver-kubernetes-1.9.6/_build:/usr/share/gocode
+ go test -buildmode pie -compiler gc -ldflags '-extldflags '\''-Wl,-z,relro  -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld '\'''
# k8s.io/apiserver/pkg/authentication/token/cache
./cache_test.go:80: Errorf format %v reads arg #3, but call has only 2 args
./cache_test.go:86: Errorf format %v reads arg #3, but call has only 2 args
FAIL	k8s.io/apiserver/pkg/authentication/token/cache [build failed]

+ GOPATH=/builddir/build/BUILD/apiserver-kubernetes-1.9.6/_build:/usr/share/gocode
+ go test -buildmode pie -compiler gc -ldflags '-extldflags '\''-Wl,-z,relro  -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld '\'''
# k8s.io/apiserver/pkg/endpoints
./apiserver_test.go:1961: Fatalf format %v reads arg #2, but call has only 1 arg
./apiserver_test.go:1965: Fatalf format %#v reads arg #2, but call has only 1 arg
./apiserver_test.go:2086: Errorf format %v reads arg #2, but call has only 1 arg
./apiserver_test.go:2091: Errorf format %#v reads arg #2, but call has only 1 arg

+ GOPATH=/builddir/build/BUILD/apiserver-kubernetes-1.9.6/_build:/usr/share/gocode
+ go test -buildmode pie -compiler gc -ldflags '-extldflags '\''-Wl,-z,relro  -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld '\'''
# k8s.io/apiserver/pkg/endpoints/filters
./audit_test.go:851: Errorf format %p has arg resp.Header.Get("Audit-ID") of wrong type string
FAIL    k8s.io/apiserver/pkg/endpoints/filters [build failed]

+ GOPATH=/builddir/build/BUILD/apiserver-kubernetes-1.9.6/_build:/usr/share/gocode
+ go test -buildmode pie -compiler gc -ldflags '-extldflags '\''-Wl,-z,relro  '\'''
# k8s.io/apiserver/pkg/storage/etcd3
./store_test.go:1196: Fatal call has possible formatting directive %v
FAIL	k8s.io/apiserver/pkg/storage/etcd3 [build failed]

And for 1.7.15:

+ GOPATH=/builddir/build/BUILD/apiserver-kubernetes-1.7.15/_build:/usr/share/gocode
+ go test -buildmode pie -compiler gc -ldflags '-extldflags '\''-Wl,-z,relro  '\'''
# k8s.io/apiserver/pkg/endpoints
./apiserver_test.go:1730: Errorf format %d has arg resp of wrong type *net/http.Response
./apiserver_test.go:1735: Errorf format %d has arg resp of wrong type *net/http.Response
FAIL	k8s.io/apiserver/pkg/endpoints [build failed]
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 25, 2018
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 25, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants