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

[Flaky test] Topology Aware Scheduling when Single TAS Resource Flavor when Nodes are created before test with rack ... #3890

Open
mimowo opened this issue Dec 19, 2024 · 7 comments · Fixed by #3891
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/flake Categorizes issue or PR as related to a flaky test.

Comments

@mimowo
Copy link
Contributor

mimowo commented Dec 19, 2024

/kind flake
/kind bug

What happened:

test flaked: TopologyAwareScheduling Suite.[It] Topology Aware Scheduling when Single TAS Resource Flavor when Nodes are created before test with rack being the lowest level should not admit the workload after the topology is deleted but should admit it after the topology is created

Failure on the 0.10 branch: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/periodic-kueue-test-integration-release-0-10/1869374748694155264

Dashboard: https://testgrid.k8s.io/sig-scheduling#periodic-kueue-test-integration-release-0-10

image

What you expected to happen:

No random failures

How to reproduce it (as minimally and precisely as possible):

CI

Anything else we need to know?:

{Timed out after 5.000s.
The function passed to Eventually failed at /home/prow/go/src/kubernetes-sigs/kueue/test/util/util.go:94 with:
Error matcher expects an error.  Got:
    <nil>: nil failed [FAILED] Timed out after 5.000s.
The function passed to Eventually failed at /home/prow/go/src/kubernetes-sigs/kueue/test/util/util.go:94 with:
Error matcher expects an error.  Got:
    <nil>: nil
In [It] at: /home/prow/go/src/kubernetes-sigs/kueue/test/integration/tas/tas_test.go:585 @ 12/18/24 13:47:48.162
}
@mimowo mimowo added the kind/bug Categorizes issue or PR as related to a bug. label Dec 19, 2024
@k8s-ci-robot k8s-ci-robot added the kind/flake Categorizes issue or PR as related to a flaky test. label Dec 19, 2024
@mimowo
Copy link
Contributor Author

mimowo commented Dec 19, 2024

cc @PBundyra @mbobrovskyi PTAL

@mimowo mimowo changed the title [Flaky test] [Flaky test] Topology Aware Scheduling when Single TAS Resource Flavor when Nodes are created before test with rack ... Dec 19, 2024
@mbobrovskyi
Copy link
Contributor

/assign

@k8s-ci-robot k8s-ci-robot reopened this Dec 23, 2024
@k8s-ci-robot
Copy link
Contributor

@mbobrovskyi: Reopened this issue.

In response to this:

/reopen

It happens again https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_kueue/3870/pull-kueue-test-integration-main/1871059509439369216.

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-sigs/prow repository.

@mbobrovskyi
Copy link
Contributor

/unassign

@mbobrovskyi
Copy link
Contributor

/assign @mykysha

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/flake Categorizes issue or PR as related to a flaky test.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants