This repository has been archived by the owner on Jun 28, 2024. It is now read-only.
integration tests for cpuset need updating #2845
Assignees
Labels
Comments
egernst
added
bug
egernst
added a commit
to egernst/tests
that referenced
this issue
Sep 10, 2020
The minimum number of CPUs were wrong. 0,2 -> [0,2] = 2, not 3. Fixes: kata-containers#2845 Signed-off-by: Eric Ernst <[email protected]>
egernst
added a commit
to egernst/tests
that referenced
this issue
Sep 10, 2020
The minimum number of CPUs were wrong. 0,2 -> [0,2] = 2, not 3. Fixes: kata-containers#2845 Signed-off-by: Eric Ernst <[email protected]>
egernst
added a commit
to egernst/tests
that referenced
this issue
Sep 10, 2020
This test will fail until we have appropriate CPUSet support inside the guest. Today CPUSets are only supported on the host, and are done by placing the entire guest into a CPUset that matches the sum of container cpusets. This isn't reflected via nproc in the guest. Fixes: kata-containers#2845 Signed-off-by: Eric Ernst <[email protected]>
egernst
added a commit
to egernst/tests
that referenced
this issue
Sep 11, 2020
This test will fail until we have appropriate CPUSet support inside the guest. Today CPUSets are only supported on the host, and are done by placing the entire guest into a CPUset that matches the sum of container cpusets. This isn't reflected via nproc in the guest. - Remove test that checked nproc - Update cpu test to check host cpuset cgroup Fixes: kata-containers#2845 Signed-off-by: Eric Ernst <[email protected]>
chavafg
pushed a commit
to chavafg/tests-1
that referenced
this issue
Oct 16, 2020
The minimum number of CPUs were wrong. sum of cpus in set 0,2 is 2, not 3. sum of cpus in set 0,3 is 2, not 3. Fixes: kata-containers#2845 Signed-off-by: Eric Ernst <[email protected]> (cherry picked from commit 2ef790b)
chavafg
pushed a commit
to chavafg/tests-1
that referenced
this issue
Oct 16, 2020
This test will fail until we have appropriate CPUSet support inside the guest. Today CPUSets are only supported on the host, and are done by placing the entire guest into a CPUset that matches the sum of container cpusets. This isn't reflected via nproc in the guest. - Remove test that checked nproc - Update cpu test to check host cpuset cgroup Fixes: kata-containers#2845 Signed-off-by: Eric Ernst <[email protected]> (cherry picked from commit d0b76d1)
chavafg
pushed a commit
to chavafg/tests-1
that referenced
this issue
Oct 16, 2020
The minimum number of CPUs were wrong. sum of cpus in set 0,2 is 2, not 3. sum of cpus in set 0,3 is 2, not 3. Fixes: kata-containers#2845 Signed-off-by: Eric Ernst <[email protected]> (cherry picked from commit 2ef790b)
chavafg
pushed a commit
to chavafg/tests-1
that referenced
this issue
Oct 16, 2020
This test will fail until we have appropriate CPUSet support inside the guest. Today CPUSets are only supported on the host, and are done by placing the entire guest into a CPUset that matches the sum of container cpusets. This isn't reflected via nproc in the guest. - Remove test that checked nproc - Update cpu test to check host cpuset cgroup Fixes: kata-containers#2845 Signed-off-by: Eric Ernst <[email protected]> (cherry picked from commit d0b76d1)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description of problem
Integration tests currently had a couple of issues:
Expected result
Tests don't assume cpusets are set in the guest.
Actual result
Test verifies that nproc is tied to cpuset size, which isn't necessarily the case at this time.
The text was updated successfully, but these errors were encountered: