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

[Failing Test] gce-master-scale-performance #118305

Closed
mehabhalodiya opened this issue May 29, 2023 · 4 comments
Closed

[Failing Test] gce-master-scale-performance #118305

mehabhalodiya opened this issue May 29, 2023 · 4 comments
Assignees
@wojtek-t
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/scalability Categorizes an issue or PR as relevant to SIG Scalability.

Comments

@mehabhalodiya
Copy link
Contributor

Which jobs are failing?

master-informing

  • gce-master-scale-performance

Which tests are failing?

  • ci-kubernetes-e2e-gce-scale-performance.Overall Changes
  • ci-kubernetes-e2e-gce-scale-performance.Pod Changes

Screenshot from 2023-05-29 07-53-35

Since when has it been failing?

2023-05-27 10:03 PDT

Testgrid link

https://testgrid.k8s.io/sig-release-master-informing#gce-master-scale-performance

Reason for failure (if possible)

Not described on the Prow dashboard

Anything else we need to know?

No response

Relevant SIG(s)

/sig scalability
cc @kubernetes/ci-signal
@mehabhalodiya mehabhalodiya added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label May 29, 2023
@k8s-ci-robot k8s-ci-robot added sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 29, 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.

@MadhavJivrajani
Copy link
Contributor

The lack of build logs leads to me to believe this was a transient failure (maybe an infra issue?), we should wait for the next run which should happen in ~9.5 hours from now (17:01 UTC) to get a better signal.

@wojtek-t
Copy link
Member

Yeah - it doesn't even seem like a test failure, rather some infra issue.

The next run is running now:
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-scale-performance/1663229036043702272

It seems ok for now, so hopefully it will pass and if so that would clearly be a "go" signal.

@wojtek-t wojtek-t self-assigned this May 29, 2023
@mehabhalodiya
Copy link
Contributor Author

Thanks all for your heads up; I see the latest run is Green.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wojtek-t wojtek-t

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/scalability Categorizes an issue or PR as relevant to SIG Scalability.
Projects
CI Signal (SIG Release / Release Team)
Status: RESOLVED
Milestone
No milestone
Development

No branches or pull requests
4 participants
@wojtek-t @MadhavJivrajani @k8s-ci-robot @mehabhalodiya