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

[Failure-test] TestLazyThroughput: total wait was: 3.145007079s; par would be ~1s #116789

Closed
pacoxu opened this issue Mar 21, 2023 · 7 comments
Closed
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@pacoxu
Copy link
Member

pacoxu commented Mar 21, 2023

Failure cluster b93b9378959634b16aeb

Error text:
Failed
=== RUN   TestLazyThroughput
    lazy_test.go:105: total wait was: 3.145007079s; par would be ~1s
--- FAIL: TestLazyThroughput (2.70s)

Recent failures:

2023/3/21 04:42:32 ci-kubernetes-unit-eks-canary
2023/3/21 03:42:33 ci-kubernetes-unit-eks-canary
2023/3/21 02:42:39 ci-kubernetes-unit-eks-canary
2023/3/21 00:42:21 ci-kubernetes-unit-eks-canary
2023/3/20 23:42:21 ci-kubernetes-unit-eks-canary

/kind failing-test

@k8s-ci-robot k8s-ci-robot added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label Mar 21, 2023
@k8s-ci-robot
Copy link
Contributor

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

  • /sig <group-name>
  • /wg <group-name>
  • /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

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 needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 21, 2023
@k8s-ci-robot
Copy link
Contributor

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.

@aojea
Copy link
Member

aojea commented Mar 21, 2023

can we get an explanation on why that is so slow?

@aojea
Copy link
Member

aojea commented Mar 21, 2023

it seems this job is experimental https://kubernetes.slack.com/archives/C09QZ4DQB/p1679410351432799
/cc @ameukam

@ameukam
Copy link
Member

ameukam commented Mar 21, 2023

ci-kubernetes-unit-eks-canary is a variant of ci-kubernetes-unit to evaluate the possibility to use EKS clusters as build clusters.

Currently working on the setup in kubernetes/k8s.io#4686.

prowjobs under sig-k8s-infra-canaries shouldn't be tracked or monitored.

@pacoxu
Copy link
Member Author

pacoxu commented Mar 23, 2023

/close

@k8s-ci-robot
Copy link
Contributor

@pacoxu: Closing this issue.

In response to this:

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

No branches or pull requests

4 participants