Skip to content

critest sometimes failed when run oom test case. #12260

@ningmingxiao

Description

@ningmingxiao

Description

default:   [FAILED] in [It] - sigs.k8s.io/cri-tools/pkg/validate/container_linux.go:165 @ 09/01/25 02:38:43.663
default:   STEP: stop PodSandbox @ 09/01/25 02:38:43.664
default:   STEP: delete PodSandbox @ 09/01/25 02:38:43.969
default:   << Timeline
default: 
default:   [FAILED] Expected
default:       <string>: Error
default:   to equal
default:       <string>: OOMKilled
default:   In [It] at: sigs.k8s.io/cri-tools/pkg/validate/container_linux.go:165 @ 09/01/25 02:38:43.663
default: ------------------------------
default: •••••••••••••••
default: 
default: Summarizing 1 Failure:
default:   [FAIL] [k8s.io] Container OOM runtime should output OOMKilled reason [It] should terminate with exitCode 137 and reason OOMKilled
default:   sigs.k8s.io/cri-tools/pkg/validate/container_linux.go:165
default: 
default: Ran 115 of 130 Specs in 52.575 seconds
default: FAIL! -- 114 Passed | 1 Failed | 0 Pending | 15 Skipped
default: 
default: 
default: Ginkgo ran 1 suite in 52.59959956s
default: 
default: Test Suite Failed
default: --- FAIL: TestCRISuite (52.61s)

Steps to reproduce the issue

Describe the results you received and expected

critest not failed.

What version of containerd are you using?

main

Any other relevant information

No response

Show configuration if it is related to CRI plugin.

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions