Bas Zalmstra

Thats a good idea! I'll add that when I have some time on my hands. :)

Im running into the same issue when running Gitlab CI with the kubernetes executor. The build job uses an alpine image which fails with: ``` Error: failed to solve: failed...

I dont exactly know what you mean. Im basically running `alpine:3.13`, I add `img` with `apk add img` and run `img build`: The gitlab ci job looks like this: ```yaml...

Im running all of this on a DigitalOcean Managed Kubernetes cluster I don't think they are using the same kernel.

Any idea why the pipelines fail? Is it because `git lfs` on CI is not the correct version?

+1

I ran into the same issue on MacOS. You can use the LLVM repository instead of extracting the llvm archives. I've managed to install llvm 7.x using pull request #59...

Would this be as simple as adding: ```cmake add_test( NAME cargo-test_${target_name} COMMAND $ test --target ${_CORROSION_RUST_CARGO_TARGET} -p ${package_name} --manifest-path ${path_to_toml} WORKING_DIRECTORY ${CMAKE_BINARY_DIR}/${build_dir} ) ``` to the `_add_cargo_build` function?

Im looking into the disk space issue.

Our build is using more than 14gb. Do you think we can remove some dependencies? Or maybe we can not build the dependencies for the benchmarks? We are not running...