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

Various failed builds of k8s.io/kubernetes/test/integration in PR builder #30754

Closed
mwielgus opened this issue Aug 17, 2016 · 13 comments
Closed

Various failed builds of k8s.io/kubernetes/test/integration in PR builder #30754

mwielgus opened this issue Aug 17, 2016 · 13 comments
Assignees
@fejta
Labels
area/kubelet area/test area/test-infra priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/storage Categorizes an issue or PR as relevant to SIG Storage.

Comments

@mwielgus
Copy link
Contributor

mwielgus commented Aug 17, 2016 •
edited by gmarek
Loading

Failed k8s.io/kubernetes/test/integration/persistentvolumes build. No extra information is available in logs.
@mwielgus mwielgus mentioned this issue Aug 17, 2016
Merged
@gmarek gmarek changed the title Build failed in k8s.io/kubernetes/test/integration/persistentvolumes Various failed builds of k8s.io/kubernetes/test/integration in PR builder Aug 17, 2016
@gmarek
Copy link
Contributor

gmarek commented Aug 17, 2016

I have one PR (#30138) that failed twice on this - first time it was k8s.io/kubernetes/test/integration/storageclasses build that failed, second time it was k8s.io/kubernetes/test/integration/kubectl. This is PR builder flakyness.

@gmarek gmarek assigned fejta and ixdy Aug 17, 2016
@gmarek gmarek mentioned this issue Aug 17, 2016
Merged
@gmarek gmarek added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Aug 17, 2016
@wojtek-t
Copy link
Member

In the last few days I've seen a number of failure from integration tests with

out of memory

I think this may be related.

@ixdy
Copy link
Member

ixdy commented Aug 17, 2016

Curious. We haven't changed anything from the test-infra side recently.

cc @kubernetes/test-infra-maintainers

@wojtek-t wojtek-t mentioned this issue Aug 18, 2016
Merged
@nikhiljindal
Copy link
Contributor

test/integration/persistentvolumes failed again in https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/30673/kubernetes-pull-test-unit-integration/40428/build-log.txt, no logs.

@nikhiljindal nikhiljindal mentioned this issue Aug 18, 2016
Merged
@fejta fejta assigned jsafrane and unassigned fejta and ixdy Aug 20, 2016
@fejta fejta added sig/storage Categorizes an issue or PR as relevant to SIG Storage. and removed area/test-infra labels Aug 20, 2016
@jsafrane
Copy link
Member

integration/persistentvolumes compiles just fine, there must be something odd in the test infrastructure. And from the logs I have no clue what could it be.

@jsafrane jsafrane assigned fejta and unassigned jsafrane Aug 22, 2016
@fejta
Copy link
Contributor

fejta commented Aug 29, 2016

No hits of this for two weeks... I suspect this was a ram issue that we resolved. Please reactivate if it is seen again...

@fejta fejta closed this as completed Aug 29, 2016
@mml mml reopened this Aug 30, 2016
@mml
Copy link
Contributor

mml commented Aug 30, 2016

See #31729. Not integration tests, but the same symptoms.

@mml
Copy link
Contributor

mml commented Aug 30, 2016

#31729 was a legit build failure, but we don't seem to save stderr. Or may be I just can't find it?

@fejta
Copy link
Contributor

fejta commented Sep 21, 2016 •
edited
Loading

We do verbose logging https://github.com/kubernetes/kubernetes/blob/master/hack/jenkins/gotest.sh#L42 but this is a separate artifact file rather than build-log.txt

Click the artifacts link in gubernator, navigate to the artfiacts folder in gcs, then open the correct .stdout file.

@fejta fejta closed this as completed Sep 21, 2016
@mml
Copy link
Contributor

mml commented Sep 21, 2016

Yeah, we save stdout, but the compiler errors are sent to stderr.

So I see

FAIL    k8s.io/kubernetes/federation/pkg/federation-controller/ingress [build failed]
FAIL    k8s.io/kubernetes/federation/pkg/federation-controller/namespace [build failed]
FAIL    k8s.io/kubernetes/federation/pkg/federation-controller/replicaset [build failed]

But the actual compiler errors aren't there.

@ixdy
Copy link
Member

ixdy commented Sep 22, 2016

The compiler errors are in the regular build log.

@gmarek
Copy link
Contributor

gmarek commented Sep 26, 2016

@fejta - can you please don't close issues that don't have gubernator links?

@gmarek gmarek reopened this Sep 26, 2016
@fejta
Copy link
Contributor

fejta commented Sep 26, 2016

Did you reopen the wrong bug? I closed the issue because all the requested info already exists (although I agree it is painfully hard to collate all the info in the right places)

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

@fejta fejta

Labels
area/kubelet area/test area/test-infra priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/storage Categorizes an issue or PR as relevant to SIG Storage.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@mml @fejta @gmarek @jsafrane @ixdy @nikhiljindal @wojtek-t @mwielgus @k8s-github-robot