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

TestConcurrentLockEntry times out #118528

Open
aojea opened this issue Jun 7, 2023 · 2 comments
Open

TestConcurrentLockEntry times out #118528

aojea opened this issue Jun 7, 2023 · 2 comments
Assignees
Labels
kind/flake Categorizes issue or PR as related to a flaky test. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@aojea
Copy link
Member

aojea commented Jun 7, 2023

Which jobs are flaking?

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/118515/pull-kubernetes-unit-go-compatibility/1666191128879173632

Which tests are flaking?

k8s.io/kubernetes/vendor/k8s.io/legacy-cloud-providers/azure: TestConcurrentLockEntry

Since when has it been flaking?

Seen here #118515

Testgrid link

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/118515/pull-kubernetes-unit-go-compatibility/1666191128879173632

Reason for failure (if possible)

The tests times out and has a name containing concurrency and lock, lots of chances there is some deadlock somewhere

{Failed  === RUN   TestConcurrentLockEntry
panic: test timed out after 3m0s
running tests:
	TestConcurrentLockEntry (1s)

goroutine 1296 [running]:

the stack trace should provide more information

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/118515/pull-kubernetes-unit-go-compatibility/1666191128879173632

Anything else we need to know?

No response

Relevant SIG(s)

/sig cloud-provider

@aojea aojea added the kind/flake Categorizes issue or PR as related to a flaky test. label Jun 7, 2023
@k8s-ci-robot k8s-ci-robot added sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jun 7, 2023
@aojea
Copy link
Member Author

aojea commented Jun 7, 2023

@bridgetkromhout you may be able to route this to the right person

@bridgetkromhout
Copy link
Member

/triage accepted
/assign

@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 Jun 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/flake Categorizes issue or PR as related to a flaky test. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants