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

Track and address skipped tests in node e2e suite #8668

Open
sohankunkerkar opened this issue Oct 11, 2024 · 1 comment
Open

Track and address skipped tests in node e2e suite #8668

sohankunkerkar opened this issue Oct 11, 2024 · 1 comment
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@sohankunkerkar
Copy link
Member

sohankunkerkar commented Oct 11, 2024

What happened?

xref: openshift/release#55802
We are currently skipping a few tests in our node e2e test suite. This issue is to track these skipped tests and work towards enabling them.

Skipped Tests

Nodeconformance

  1. [sig-node] Summary API [NodeConformance] when querying /stats/summary should report resource usage through the stats apiChanges
  2. [sig-node] MirrorPodWithGracePeriod when create a mirror pod and the container runtime is temporarily down during pod termination [NodeConformance] [Serial] [Disruptive]

Conformance

  1. [sig-node] Pods should delete a collection of pods [Conformance]
  2. [sig-node] Pods should patch a pod status [Conformance]
  3. [sig-node] Pods should run through the lifecycle of Pods and PodStatus [Conformance]

Nodefeature

  1. ProcMountType [this requires a separate periodic job]
  2. CheckpointContainer [not supported in crun]

What did you expect to happen?

Those tests should pass

How can we reproduce it (as minimally and precisely as possible)?

https://prow.ci.openshift.org/?job=rehearse-55802-periodic-ci-cri-o-cri-o-main-periodics-crio-node-e2e-*-periodic

Anything else we need to know?

No response

CRI-O and Kubernetes version

$ crio --version
latest
$ kubectl version --output=json
# paste output here

OS version

N/A

Additional environment details (AWS, VirtualBox, physical, etc.)

@sohankunkerkar sohankunkerkar added kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. kind/test-flake Categorizes issue or PR as related to test flakes. labels Oct 11, 2024
Copy link

A friendly reminder that this issue had no activity for 30 days.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 11, 2024
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. kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

1 participant