-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
Static Docker containers need to be restarted with --cpuset-cpus="0-3"
#3375
Comments
--cpuset-cpus="0-3"
--cpuset-cpus="0-3"
@Haroon-Khel Is test-docker-sles15-armv8l-1 based on the BCI image referenced in #3135? |
Note: This PR should cap test concurrency to either:
Whichever is smaller. Also, we calculate "memory" as either the machine memory of the cgroup (container) memory, whichever is smaller. |
✅ Implies the containers have been rerun with
|
Annoyingly to rerun a container with different parameters, it isnt as simple as |
I wont restart the x64 equinix nodes as we want to start decommissiong those nodes as anyway as per #3378 (comment) |
With the x64 equinix dockerhost machines decommissioned, theres just the ppc64le nodes on dockerhost-osuosl-ubuntu2004-ppc64le-1 left |
dockerhost-osuosl-ubuntu2004-ppc64le-1 nodes have been restarted. Issue is closed |
ref #3360 (comment)
All of our containers need to be restarted with the proper command to assign 4 cpus. The command
--cpuset-cpus="0-3"
needs to be used instead of--cpus=4.0
. That way the test jobs can properly read the number of cpus on the container, instead of reading 160 cores on the dockerhost, and then assigning the appropriate concurrency. At the moment test jobs are running with-concurrency:81
on the containers while it should be-concurrency:3
The following nodes have been restarted with
--cpuset-cpus="0-3"
dockerhost-equinix-ubuntu2204-armv8l-1
dockerhost-equinix-ubuntu2004-armv8l-1
The text was updated successfully, but these errors were encountered: