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

scheduler integration tests timing out on server setup #113207

Open
alculquicondor opened this issue Oct 20, 2022 · 8 comments
Open

scheduler integration tests timing out on server setup #113207

alculquicondor opened this issue Oct 20, 2022 · 8 comments
Labels
kind/flake Categorizes issue or PR as related to a flaky test. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/testing Categorizes an issue or PR as relevant to SIG Testing. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@alculquicondor
Copy link
Member

Which jobs are flaking?

pull-kubernetes-integration

Which tests are flaking?

It looks like random tests are failing, for example:

  • TestUnReserveReservePlugins/The_Reserve_plugins_succeed
  • TestImageLocalityScoring
  • TestPVCBoundWithADC

Since when has it been flaking?

Oct 19th

Testgrid link

https://storage.googleapis.com/k8s-triage/index.html?pr=1&job=pull-kubernetes-integration&test=scheduler

Reason for failure (if possible)

    test_server.go:221: timed out waiting for the condition

Anything else we need to know?

It doesn't look like the error is specific to the tests, so maybe something changed in the apiserver setup recently

Relevant SIG(s)

/sig scheduling
/sig testing
/sig api-machinery
@alculquicondor alculquicondor added the kind/flake Categorizes issue or PR as related to a flaky test. label Oct 20, 2022
@k8s-ci-robot k8s-ci-robot added sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/testing Categorizes an issue or PR as relevant to SIG Testing. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 20, 2022
@alculquicondor alculquicondor mentioned this issue Oct 20, 2022
Merged
@pohly
Copy link
Contributor

pohly commented Oct 20, 2022

Perhaps related to #111339?

Does that apiserver do anything with stdout?

@pohly
Copy link
Contributor

pohly commented Oct 20, 2022

Never mind. The integration tests aren't using Ginkgo.

@leilajal
Copy link
Contributor

@alculquicondor thanks for sending the PR! Is it fixed?
/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 20, 2022
@alculquicondor
Copy link
Member Author

This is not a PR, just a report.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/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 Jan 18, 2023
@vaibhav2107
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 15, 2023
@k8s-triage-robot
Copy link

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

  • Confirm that this issue is still relevant with /triage accepted (org members only)
  • Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. and removed triage/accepted Indicates an issue or PR is ready to be actively worked on. labels May 14, 2024
@fedebongio
Copy link
Contributor

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/flake Categorizes issue or PR as related to a flaky test. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/testing Categorizes an issue or PR as relevant to SIG Testing. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
SIG Scheduling
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
7 participants
@pohly @alculquicondor @fedebongio @k8s-ci-robot @k8s-triage-robot @leilajal @vaibhav2107