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

flakey npd tests in sig-node ci jobs #467

Closed
MHBauer opened this issue Sep 17, 2020 · 8 comments
Closed

flakey npd tests in sig-node ci jobs #467

MHBauer opened this issue Sep 17, 2020 · 8 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@MHBauer
Copy link

MHBauer commented Sep 17, 2020

I've documented at k/k repo before realizing this has it's own repo. Maybe you can help me debug?
kubernetes/kubernetes#94493
Are these tests supposed to be running outside of the ci-npd jobs?
Do they need to be ignored?
Is there some special setup that is done?
Should they be marked [serial] or [disruptive]?

@vteratipally
Copy link
Collaborator

vteratipally commented Sep 25, 2020

these tests might be added as NPD runs as a default on kubernetes. I will try to debug the issue. I dont think there is any special setup done here. needs to be marked serial

@SergeyKanzhelev
Copy link
Member

@vteratipally can you comment on why serial is needed? What tests do that wouldn't run in parellel? Can the un-parallellable resources be named somehow to separate tests?

@vteratipally
Copy link
Collaborator

Yes can we can try to separate the tests to parallelable resource because I believe that these tests are based on the event logs. I can give it a try

@SergeyKanzhelev
Copy link
Member

SergeyKanzhelev commented Nov 5, 2020

CC: @ForestCold FYI

@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 Feb 3, 2021
@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-contributor-experience at kubernetes/community.
/lifecycle rotten

@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 Mar 5, 2021
@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-contributor-experience at kubernetes/community.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

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-contributor-experience at kubernetes/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

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

5 participants