swap-conformance: run memory eviction tests

[iholder101]

Start running memory eviction tests on the swap-conformance lane.

This was already tried in #34507 and later reverted in #34558.

However, after trying to run this locally with:

make test-e2e-node PARALLELISM=1 CLEANUP=true DELETE_INSTANCES=true FOCUS="NodeSwap|MemoryAllocatableEviction|PriorityMemoryEvictionOrdering" SKIP="dummy" SSH_USER="core" KUBE_SSH_USER=core REMOTE=true RUNTIME=remote USE_DOCKERIZED_BUILD=false IMAGE_CONFIG_FILE="/workspace/test-infra/jobs/e2e_node/swap/image-config-swap-fedora.yaml" CONTAINER_RUNTIME_ENDPOINT="unix:///var/run/crio/crio.sock" TEST_ARGS='--kubelet-flags="--fail-swap-on=false --cgroup-driver=systemd --cgroups-per-qos=true --cgroup-root=/  --runtime-cgroups=/system.slice/crio.service --kubelet-cgroups=/system.slice/kubelet.service" --extra-log="{"name": "crio.log", "journalctl": ["-u", "crio"]}" --feature-gates=NodeSwap=true --service-feature-gates="NodeSwap=true"'

all of the tests passed (for multiple times):

Ran 14 of 793 Specs in 1576.462 seconds
SUCCESS! -- 14 Passed | 0 Failed | 0 Pending | 779 Skipped
PASS

I suspect that the previous problem was due to the fact we lacked the --parallelism=1 parameter that is now added as part of this PR.

/sig node
/cc @kannon92

[iholder101]

/test ?

[k8s-ci-robot]

@iholder101: The following commands are available to trigger required jobs:

/test pull-test-infra-gubernator

/test pull-test-infra-misc-image-build-test

/test pull-test-infra-prow-checkconfig

/test pull-test-infra-unit-test

/test pull-test-infra-verify-cri-o

/test pull-test-infra-verify-lint

The following commands are available to trigger optional jobs:

/test pull-test-infra-unit-test-race-detector-nonblocking

Use /test all to run the following jobs that were automatically triggered:

pull-test-infra-gubernator

pull-test-infra-prow-checkconfig

pull-test-infra-unit-test

pull-test-infra-unit-test-race-detector-nonblocking

pull-test-infra-verify-lint

In response to this:

/test ?

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-sigs/prow repository.

[kannon92]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: iholder101, kannon92

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• config/jobs/kubernetes/sig-node/OWNERS [kannon92]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@iholder101: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key node-kubelet.yaml using file config/jobs/kubernetes/sig-node/node-kubelet.yaml
• key sig-node-presubmit.yaml using file config/jobs/kubernetes/sig-node/sig-node-presubmit.yaml

In response to this:

Start running memory eviction tests on the swap-conformance lane.

This was already tried in #34507 and later reverted in #34558.

However, after trying to run this locally with:

make test-e2e-node PARALLELISM=1 CLEANUP=true DELETE_INSTANCES=true FOCUS="NodeSwap|MemoryAllocatableEviction|PriorityMemoryEvictionOrdering" SKIP="dummy" SSH_USER="core" KUBE_SSH_USER=core REMOTE=true RUNTIME=remote USE_DOCKERIZED_BUILD=false IMAGE_CONFIG_FILE="/workspace/test-infra/jobs/e2e_node/swap/image-config-swap-fedora.yaml" CONTAINER_RUNTIME_ENDPOINT="unix:///var/run/crio/crio.sock" TEST_ARGS='--kubelet-flags="--fail-swap-on=false --cgroup-driver=systemd --cgroups-per-qos=true --cgroup-root=/  --runtime-cgroups=/system.slice/crio.service --kubelet-cgroups=/system.slice/kubelet.service" --extra-log="{"name": "crio.log", "journalctl": ["-u", "crio"]}" --feature-gates=NodeSwap=true --service-feature-gates="NodeSwap=true"'

all of the tests passed (for multiple times):

Ran 14 of 793 Specs in 1576.462 seconds
SUCCESS! -- 14 Passed | 0 Failed | 0 Pending | 779 Skipped
PASS

I suspect that the previous problem was due to the fact we lacked the --parallelism=1 parameter that is now added as part of this PR.

/sig node
/cc @kannon92

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-sigs/prow repository.