Random fails when building within github actions

[johanneskoester]

We try to build a container image via cargo wharf. Locally everything works fine. However, in github actions we have failures at random crates (everytime a different one). The errors always look like this:

#375 Compiling unic-char-range
#375 ERROR: executor failed running [rustc --edition=2018 --crate-name unic_char_range /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/unic-char-range-0.9.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 --cfg feature="default" -C metadata=3b7b6d2f09242336 -C extra-filename=-3b7b6d2f09242336 --out-dir /target/release/deps -L dependency=/target/release/deps --cap-lints allow]: flightcontrol: exceeded retry timeout

We suspect it might be due to the implicit parallelization. Is it possible to limit it somehow? Or do you have another hint about the error?

[chris13524]

We are also seeing the same issue, but it is consistent for us:

#262 Compiling signature
#262 ERROR: executor failed running [rustc --edition=2018 --crate-name signature /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/signature-1.2.2/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 --cfg feature="std" -C metadata=e1d46eb5baa92a7c -C extra-filename=-e1d46eb5baa92a7c --out-dir /target/release/deps -L dependency=/target/release/deps --cap-lints allow]: flightcontrol: exceeded retry timeout