AI_Assistant/pcbjam
Watch
1
0
Fork
You've already forked pcbjam
 0
Code Issues Pull requests Projects Releases 4 Packages Wiki Activity Actions 2

fix(ci): ubicloud docker rejects cpus limit == host CPUs — cap at nproc-1

Browse source 
Run 27330725978 died at container create: "range of CPUs is from 0.01 to
30.00, as there are only 30 CPUs available" with KICAD_DOCKER_CPUS=30 on the
30-vcpu standard-30. The Hetzner box (fresh docker-ce) accepts cpus == nproc;
Ubicloud's preinstalled daemon doesn't. A 29/30 CFS quota is noise.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Istvan Matejcsok 2026-06-11 09:26:56 +02:00
commit 775b657b89
1 changed files with 4 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

5
.github/workflows/ci-ubicloud.yml vendored
View file

@ -54,7 +54,10 @@ jobs:
# asyncify+-O2 with the next tool's container compile — same tuning
# as the Hetzner workflow (rationale in ci-full-build.yml and
# docs/ci-build-slowness-findings.md). standard-30: 30 vcpu / 120 GB.
export KICAD_DOCKER_CPUS="$(nproc)" KICAD_DOCKER_MEM=110G
# nproc-1: Ubicloud's preinstalled docker daemon rejects a cpus limit
# equal to the host CPU count ("range of CPUs is from 0.01 to 30.00",
# run 27330725978); the Hetzner box accepted 32-of-32.
export KICAD_DOCKER_CPUS="$(( $(nproc) - 1 ))" KICAD_DOCKER_MEM=110G
export KICAD_PIPELINE=1 BINARYEN_CORES=16
# Self-built wasm-opt: official x86_64-linux tarballs run asyncify
# ~4x slower than a stock gcc -O3+LTO build (A/B run 27276830256).