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

k8s.io/kubernetes/pkg/master TestValidOpenAPISpec #39604

Closed
0xmichalis opened this issue Jan 9, 2017 · 12 comments · Fixed by #39649
Closed

k8s.io/kubernetes/pkg/master TestValidOpenAPISpec #39604

0xmichalis opened this issue Jan 9, 2017 · 12 comments · Fixed by #39649
Assignees
Labels
area/test kind/flake Categorizes issue or PR as related to a flaky test. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.

Comments

@0xmichalis
Copy link
Contributor

Haven't seen this one before and I am not sure it has any relation with the PR that hit it.
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/36243/pull-kubernetes-unit/12124/

@kubernetes/sig-testing-misc

@0xmichalis 0xmichalis added area/test kind/flake Categorizes issue or PR as related to a flaky test. labels Jan 9, 2017
@fraenkel
Copy link
Contributor

fraenkel commented Jan 9, 2017

From what I can gather, it is being killed due to taking over 5 minutes which is roughly how long it takes (~300s) on successful unit builds.

@deads2k
Copy link
Contributor

deads2k commented Jan 9, 2017

bumping priority. I'm seeing this pretty frequently this morning.

@mbohlool I see OpenAPI and associate you. You know something about this one?

@mbohlool
Copy link
Contributor

mbohlool commented Jan 9, 2017

@deads2k Yes, I wrote this test. It was failing (timing out) for quite some time on jenkins but passing quite fast locally. I've disabled it but after a while it started passing and I assumed it was a configuration change on test machines. I will spend some time on it again to see if I can find the root cause and will disable it otherwise.

@@kubernetes/sig-testing-misc, This test is passing locally in about 15 second. Do you have any idea why it is timing out (or passing near to 300s) on jenkins machines?

@fraenkel where do you see the successful test stats?

@fraenkel
Copy link
Contributor

fraenkel commented Jan 9, 2017

@mbohlool I see what you do. Locally it takes 25s, with bots it is 300s. My guess is that we are constrained by CPU and all the encode/decode is causing strain either on CPU or GC. The bots fail about 75% for me so I just keep retrying until success. Just had 2 this morning pass at 296s.

@spxtr
Copy link
Contributor

spxtr commented Jan 9, 2017

Curiously, it's taking about 20 seconds with Bazel. @rmmh, this might be worth looking at.

@ixdy
Copy link
Member

ixdy commented Jan 9, 2017

I think we run tests in Jenkins with -race, which might explain the slowness?

@spxtr
Copy link
Contributor

spxtr commented Jan 10, 2017

@fraenkel
Copy link
Contributor

-race does kill the performance, 25s -> 166s which is on par with bazel.

@mbohlool
Copy link
Contributor

is it possible to disable -race for this test? and should we do that if it is possible?

@deads2k deads2k added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. priority/P0 and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jan 10, 2017
@deads2k
Copy link
Contributor

deads2k commented Jan 10, 2017

Now blocking the submit queue.

@spxtr spxtr reopened this Jan 10, 2017
@mbohlool
Copy link
Contributor

I think I am missing something here. I've checked some of the attached PRs. Links to the pkg/master folder in master branch has the change (new file called master_openapi_test.go:

https://github.com/kubernetes/kubernetes/blob/master/pkg/master/master_openapi_test.go

but non of the recent PRs I checked has the file in their branch:

https://github.com/deads2k/kubernetes/tree/generic-17-move-tests/pkg/master
https://github.com/rf232/kubernetes/tree/dashboard-v1.5.1/pkg/master
https://github.com/kargakis/kubernetes/tree/unit-tests-for-the-d-controller/pkg/master

That means they didn't sync with master? What am I missing here?

@mbohlool
Copy link
Contributor

OK. I see, the tests are patching the change of the PR into the master, so everybody should get that if they retest, but it look like my test is not blocking submit queue. there should be another issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/test kind/flake Categorizes issue or PR as related to a flaky test. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants