Compilation fails in GitLab CI #3
Comments
|
Kind of weird. For example this Docker image project makes also CI via Github Actions + Docker just performing a simple Did you indicate the CC and CXX environment variables too? Maybe some of your crates requires so? |
|
There's no native code so CC/CXX shouldn't have been required. What's confusing me is that it works in docker but the exact same(?) command fails in CI. Here's a job I did with CC/CXX set, printing out env before the run, and noting that it's using the correct o64-clang executables. Maybe you can spot something odd in here? |
|
It looks like your pipeline setup is fine and yeah your project doesn't require C linkage. So I did a quick test on my Drone CI to try to reproduce it but I couldn't. ---
kind: pipeline
type: docker
name: development
platform:
os: linux
arch: amd64
steps:
- name: restore-cache
image: drillster/drone-volume-cache
volumes:
- name: cache
path: /cache
settings:
restore: true
mount:
- ./target
- name: test
image: joseluisq/rust-linux-darwin-builder:1.52.1
commands:
- env
- which o64-clang
- which o64-clang++
- cargo build --release --target=x86_64-apple-darwin
- name: rebuild-cache
image: drillster/drone-volume-cache
volumes:
- name: cache
path: /cache
settings:
rebuild: true
mount:
- ./target
volumes:
- name: cache
host:
path: /tmp/cacheNo explicit CC or CXX envs needed. You can also just ignore the cache steps.
Perhaps the issue relates to your CI cache mechanism, lack of privileges (not sure really) or maybe you are facing something like this issue. But unfortunately I'm just guessing. Anyway since I can not reproduce the issue via Docker on Drone CI or Github Actions. And since it seems not directly related to this Docker image, I'm going to close the issue for now. However feel free to re-open it if needed. |
|
I face the exact same problem, it works in docker but fails in Gitlab CI with the same error. I am specifying |
|
I will try to give it a second look at this. I will let you know here. |
|
Steps to reproduce: |
|
For what it's worth, I did open an issue on the GitLab tracker but it has seen no activity since. |
|
I addressed the "issue" that was really not but instead an extra line missing to append to your pipeline scripts before cross-compile your program. ~> gitlab-runner exec docker x86_64-apple-darwin
Runtime platform arch=amd64 os=linux pid=28513 revision=8925d9a0 version=14.1.0
Running with gitlab-runner 14.1.0 (8925d9a0)
Preparing the "docker" executor
Using Docker executor with image joseluisq/rust-linux-darwin-builder:1.54.0 ...
Authenticating with credentials from /home/joseluisq/.docker/config.json
Pulling docker image joseluisq/rust-linux-darwin-builder:1.54.0 ...
Using docker image sha256:e808e07975ccc5746a678ad672b6b5330cbdc73b919483406b4378710513ebd5 for joseluisq/rust-linux-darwin-builder:1.54.0 with digest joseluisq/rust-linux-darwin-builder@sha256:67afeff25184a518dd047127f320ec417ce3b773706cddfd2efd10f04ca7aa7f ...
Preparing environment
Running on runner--project-0-concurrent-0 via quintana...
Getting source from Git repository
Fetching changes...
Initialized empty Git repository in /builds/project-0/.git/
Created fresh repository.
Checking out d0a8fdfe as master...
Skipping Git submodules setup
ERROR: Could not create cache adapter error=cache factory not found: factory for cache adapter "" was not registered
Restoring cache
Checking cache for one-key-to-rule-them-all...
No URL provided, cache will not be downloaded from shared cache server. Instead a local version of cache will be extracted.
Successfully extracted cache
Executing "step_script" stage of the job script
Using docker image sha256:e808e07975ccc5746a678ad672b6b5330cbdc73b919483406b4378710513ebd5 for joseluisq/rust-linux-darwin-builder:1.54.0 with digest joseluisq/rust-linux-darwin-builder@sha256:67afeff25184a518dd047127f320ec417ce3b773706cddfd2efd10f04ca7aa7f ...
$ rustc --version && cargo --version
rustc 1.54.0 (a178d0322 2021-07-26)
cargo 1.54.0 (5ae8d74b3 2021-06-22)
$ cp /root/.cargo/config "$CARGO_HOME/"
$ cargo build --release --target=x86_64-apple-darwin
Updating crates.io index
Downloading crates ...
Downloaded signal-hook v0.1.17
Downloaded crossterm v0.18.2
Downloaded lazy_static v1.4.0
Downloaded log v0.4.14
Downloaded parking_lot_core v0.8.3
Downloaded mio v0.7.13
Downloaded lock_api v0.4.4
Downloaded bitflags v1.3.2
Downloaded instant v0.1.10
Downloaded scopeguard v1.1.0
Downloaded parking_lot v0.11.1
Downloaded cfg-if v1.0.0
Downloaded smallvec v1.6.1
Downloaded signal-hook-registry v1.4.0
Downloaded libc v0.2.99
Compiling libc v0.2.99
Compiling cfg-if v1.0.0
Compiling log v0.4.14
Compiling smallvec v1.6.1
Compiling scopeguard v1.1.0
Compiling bitflags v1.3.2
Compiling lazy_static v1.4.0
Compiling instant v0.1.10
Compiling lock_api v0.4.4
Compiling signal-hook-registry v1.4.0
Compiling parking_lot_core v0.8.3
Compiling mio v0.7.13
Compiling parking_lot v0.11.1
Compiling signal-hook v0.1.17
Compiling crossterm v0.18.2
Compiling inquirs v0.1.0 (/builds/project-0)
Finished release [optimized] target(s) in 38.89s
ERROR: Could not create cache adapter error=cache factory not found: factory for cache adapter "" was not registered
ERROR: Could not create cache adapter error=cache factory not found: factory for cache adapter "" was not registered
ERROR: Could not create cache adapter error=cache factory not found: factory for cache adapter "" was not registered
Saving cache for successful job
Creating cache one-key-to-rule-them-all...
WARNING: /builds/project-0/.cargo/bin: no matching files
/builds/project-0/.cargo/registry/index: found 84 matching files and directories
/builds/project-0/.cargo/registry/cache: found 17 matching files and directories
WARNING: /builds/project-0/.cargo/git/db: no matching files
No URL provided, cache will be not uploaded to shared cache server. Cache will be stored only locally.
Created cache
Job succeededand the Gitlab pipeline used: x86_64-apple-darwin:
stage: build
image: joseluisq/rust-linux-darwin-builder:1.54.0
artifacts:
paths:
- target/x86_64-apple-darwin/release/$CI_PROJECT_NAME
script:
- cp /root/.cargo/config "$CARGO_HOME/"
- cargo build --release --target=x86_64-apple-darwinThe "problem" was that your Gitlab pipeline uses a custom working directory that obviously is lacking some setup necessary to tell Cargo about the right linker to use for the particular target ( Of course this is not an issue with this Docker image however clarifying it on the |
|
Thank you for the thorough investigation. I guess the culprit was that I redefined CARGO_HOME in order to retain cache between builds. I'm not too familiar with the Cargo toolchain, I assume there's no way to have multiple CARGO_HOMEs? |
|
Looks like to have multiple Cargo homes is not possible. |
|
BTW I have clarified this use case in the README file. |
I wanted to use this image to automatically build macOS binaries but it's not working out for some reason.
When I ran the image using podman on the same server it does work, though.
in CI:
https://gitgud.io/nixx/inquirs/-/jobs/155135
I hope you can at least give me some advice on why this may be happening.
The text was updated successfully, but these errors were encountered: