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

[Failing test] ci-kubernetes-unit test failing #110867

Closed
gnoam opened this issue Jun 29, 2022 · 3 comments
Closed

[Failing test] ci-kubernetes-unit test failing #110867

gnoam opened this issue Jun 29, 2022 · 3 comments
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/testing Categorizes an issue or PR as relevant to SIG Testing.

Comments

@gnoam
Copy link

gnoam commented Jun 29, 2022

Which jobs are failing?

sig-release-master-blocking: ci-kubernetes-unit

Which tests are failing?

k8s.io/kubernetes/pkg/kubelet/nodeshutdown.TestMain

Since when has it been failing?

28-06-2022

Testgrid link

https://testgrid.k8s.io/sig-release-master-blocking#ci-kubernetes-unit

Reason for failure (if possible)

 W0628 22:00:17.460786   67293 mutation_detector.go:53] Mutation detector is enabled, this will result in memory leakage.
    volume_binding_test.go:625: Feed testing data and wait for them to be synced
    volume_binding_test.go:639: Start informer factory after initialization
    volume_binding_test.go:642: Wait for all started informers' cache were synced
    volume_binding_test.go:645: Verify
    volume_binding_test.go:656: Verify: call PreFilter and check status
    volume_binding_test.go:659: filter prefilter status does not match: &{1 [error getting PVC "default/pvc-1": could not find v1.PersistentVolumeClaim "default/pvc-1"] 0xc000426b20 }, want: <nil>
    --- FAIL: TestVolumeBinding/local_volumes_with_close_capacity_are_preferred_(multiple_pvcs) (0.07s)

Anything else we need to know?

No response

Relevant SIG(s)

/sig testing
cc @kubernetes/ci-signal

@gnoam gnoam added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label Jun 29, 2022
@k8s-ci-robot k8s-ci-robot added the sig/testing Categorizes an issue or PR as relevant to SIG Testing. label Jun 29, 2022
@k8s-ci-robot
Copy link
Contributor

@gnoam: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jun 29, 2022
@gnoam gnoam changed the title ci-kubernetes-unit test failing [Failing test] ci-kubernetes-unit test failing Jun 29, 2022
@pohly
Copy link
Contributor

pohly commented Jun 29, 2022

/close

This is a duplicate of #110854.

@k8s-ci-robot
Copy link
Contributor

@pohly: Closing this issue.

In response to this:

/close

This is a duplicate of #110854.

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
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
Development

No branches or pull requests

3 participants