Skip to content
This repository has been archived by the owner on May 6, 2020. It is now read-only.

Skip and fix CPU test #936

Open
1 of 2 tasks
devimc opened this issue Mar 2, 2018 · 0 comments
Open
1 of 2 tasks

Skip and fix CPU test #936

devimc opened this issue Mar 2, 2018 · 0 comments
Assignees

Comments

@devimc
Copy link

devimc commented Mar 2, 2018

@devimc devimc self-assigned this Mar 2, 2018
@devimc devimc mentioned this issue Mar 2, 2018
1 task
devimc pushed a commit to devimc/tests that referenced this issue Mar 14, 2018
Fix CPU tests according with the new changes introduced in virtcontainers.
Before starting with the tests, a container whithout CPU constraints
is launched to get the default number of vCPUs, this number is used
to calculate the expected number of vCPUs per container in each test.

fixes clearcontainers#936

Signed-off-by: Julio Montes <[email protected]>
devimc pushed a commit to devimc/tests that referenced this issue Mar 15, 2018
Fix CPU tests according with the new changes introduced in virtcontainers.
Before starting with the tests, a container whithout CPU constraints
is launched to get the default number of vCPUs, this number is used
to calculate the expected number of vCPUs per container in each test.

fixes clearcontainers#936

Signed-off-by: Julio Montes <[email protected]>
devimc pushed a commit to devimc/tests that referenced this issue Mar 15, 2018
Fix CPU tests according with the new changes introduced in virtcontainers.
Before starting with the tests, a container whithout CPU constraints
is launched to get the default number of vCPUs, this number is used
to calculate the expected number of vCPUs per container in each test.

fixes clearcontainers#936

Signed-off-by: Julio Montes <[email protected]>
mcastelino pushed a commit to mcastelino/tests that referenced this issue Jan 23, 2019
…killall

cleanup: don't use killall, replace with kill
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant