Skip to content

verify: conformance-yaml, e2e-images, should not take >3m #130756

New issue
New issue
Open
Open
verify: conformance-yaml, e2e-images, should not take >3m#130756
Labels
needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.sig/testingCategorizes an issue or PR as relevant to SIG Testing.
@BenTheElder

Description

@BenTheElder
BenTheElder
opened on Mar 12, 2025

This should be quick, what are we doing?

Verify is taking >1h, with 7 cores. Some of these stand out as likely excessively slow:

verify: conformance-yaml 3m15s
verify: e2e-images 3m38s
verify: e2e-suites 4m3s

https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/batch/pull-kubernetes-verify/1899891120544944128

/sig testing
cc @pohly @dims @aojea

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.sig/testingCategorizes an issue or PR as relevant to SIG Testing.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions