Skip to content

abuild.conf: don't export CARGO_BUILD_JOBS

omni requested to merge omni/abuild:unset-cargo-build-jobs into master

cargo build.jobs should default to number of logical CPUs anyway and setting it like this had at least gitlab CI pipelines get stuck at or right after crate downloads.

Found in aports!20973 (closed)

Merge request reports