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

Unit/integration tests timing out #23879

Closed
ikehz opened this issue Apr 5, 2016 · 8 comments
Closed

Unit/integration tests timing out #23879

ikehz opened this issue Apr 5, 2016 · 8 comments
Assignees
@ixdy
Labels
area/test-infra kind/flake Categorizes issue or PR as related to a flaky test.

Comments

@ikehz
Copy link
Contributor

ikehz commented Apr 5, 2016

https://console.cloud.google.com/storage/browser/kubernetes-jenkins/pr-logs/pull/22962/kubernetes-pull-test-unit-integration/20155/

Build timed out (after 60 minutes). Marking the build as aborted.
Build timed out (after 60 minutes). Marking the build as failed.
FATAL: Unable to delete script file /tmp/hudson1095119725192734885.sh
@ikehz ikehz added area/test-infra kind/flake Categorizes issue or PR as related to a flaky test. labels Apr 5, 2016
@ikehz ikehz mentioned this issue Apr 5, 2016
Merged
@spxtr
Copy link
Contributor

spxtr commented Apr 5, 2016

Might be a Jenkins bug.

https://issues.jenkins-ci.org/browse/JENKINS-12235

@fejta
Copy link
Contributor

fejta commented Apr 7, 2016

@ixdy this looks like a repeat of #23200

godep: [WARNING]: godep should only be used inside a valid go package directory and
godep: [WARNING]: may not function correctly. You are probably outside of your $GOPATH.
godep: [WARNING]:   Current Directory: /go/src/k8s.io/kubernetes
godep: [WARNING]:   $GOPATH: /go/src/k8s.io/kubernetes/_output/local/go:/go/src/k8s.io/kubernetes/Godeps/_workspace
godep: WARNING: Go version (go1.6) & $GO15VENDOREXPERIMENT= wants to enable the vendor experiment, but disabling because a Godep workspace (Godeps/_workspace) exists

The result is jenkins takes twenty minutes to start unit testing (the verify-all.sh stamp is utc):

+ ./hack/build-go.sh
Go version: go version go1.6 linux/amd64
+++ [0404 14:25:09] Building go targets for linux/amd64:
+ ./hack/verify-all.sh -v
--2016-04-04 21:32:55--  https://raw.githubusercontent.com/kubernetes/kubernetes/master/pkg/api/v1/register.go

+ ./hack/test-go.sh
Running tests for APIVersion: v1,extensions/v1beta1,metrics/v1alpha1 with etcdPrefix: registry
+++ [0404 14:50:08] Running tests without code coverage

@lavalamp lavalamp mentioned this issue Apr 8, 2016
Merged
@gmarek gmarek mentioned this issue Apr 15, 2016
Merged
@wojtek-t wojtek-t mentioned this issue Apr 16, 2016
Merged
@goltermann goltermann mentioned this issue Apr 18, 2016
Merged
@ixdy
Copy link
Member

ixdy commented May 5, 2016

There haven't been any PRs linked here recently, so I wonder if this is still an issue.

@ixdy
Copy link
Member

ixdy commented May 9, 2016

The tests occasionally take ~1h instead of ~45m, but the timeout is set at 1h20, so there haven't been any recent failures.

@ixdy ixdy closed this as completed May 9, 2016
@brendandburns brendandburns reopened this Jun 4, 2016
@brendandburns
Copy link
Contributor

I just had one take > 80 minutes:

#25894

@brendandburns brendandburns mentioned this issue Jun 4, 2016
Merged
@ixdy
Copy link
Member

ixdy commented Jun 4, 2016

@brendandburns please link to the log when you report flakes. it is difficult to find the failing run otherwise.

@ixdy
Copy link
Member

ixdy commented Jun 4, 2016

In this case it was kubernetes-jenkins/pr-logs/pull/25894/kubernetes-pull-test-unit-integration/29066/, but it will save everyone time if you link the logs.

@wojtek-t
Copy link
Member

wojtek-t commented Jun 8, 2016

Can we close it as duplicate of #25940 ?

@ixdy ixdy closed this as completed Jun 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ixdy ixdy

Labels
area/test-infra kind/flake Categorizes issue or PR as related to a flaky test.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@ikehz @fejta @brendandburns @spxtr @ixdy @wojtek-t