trunk
trunk copied to clipboard
CircleCI can't build using 'trunk build' with error: Blocking waiting for file lock on package cache
here is stack:
circleci local execute --job build-fromkos Fetching latest build environment... Docker image digest: sha256:99594af5fc8997d16fff35b757982b72e47c8ceebf833e99b05559c216545e65 ====>> Spin up environment Build-agent version () System information: Server Version: 20.10.16 Storage Driver: overlay2 Backing Filesystem: extfs Cgroup Driver: systemd Cgroup Version: 2 Kernel Version: 5.15.0-30-generic Operating System: Ubuntu 22.04 LTS OSType: linux Architecture: x86_64
Starting container rust:latest rust:latest: using image rust@sha256:48d3b5baf199dc7c378e775c47b0c40aaf7d8b23eaf67e15b095bbdaaecd1f10 pull stats: Image was already available so the image was not pulled time to create container: 100ms Creating Docker containers in parallel Warning: No authentication provided, using CircleCI credentials for pulls from Docker Hub. Time to upload agent and config: 2.764724592s Time to start containers: 453.183342ms WARN: Missing API Key. ====>> Preparing environment variables Using build environment variables: BASH_ENV=/tmp/.bash_env-localbuild-1653180056 CI=true CIRCLECI=true CIRCLE_BRANCH= CIRCLE_BUILD_NUM= CIRCLE_JOB=build-fromkos CIRCLE_NODE_INDEX=0 CIRCLE_NODE_TOTAL=1 CIRCLE_REPOSITORY_URL= CIRCLE_SHA1= CIRCLE_SHELL_ENV=/tmp/.bash_env-localbuild-1653180056 CIRCLE_WORKING_DIRECTORY=~/project
The redacted variables listed above will be masked in run step output.====>> Checkout code
Making checkout directory "/root/project"
Copying files from "/tmp/_circleci_local_build_repo" to "/root/project"
====>> git clone https://github.com/thedodd/ybc.git
#!/bin/bash -eo pipefail
git clone https://github.com/thedodd/ybc.git
Cloning into 'ybc'...
remote: Enumerating objects: 372, done.
remote: Counting objects: 100% (167/167), done.
remote: Compressing objects: 100% (32/32), done.
remote: Total 372 (delta 154), reused 135 (delta 135), pack-reused 205
Receiving objects: 100% (372/372), 125.78 KiB | 1.61 MiB/s, done.
Resolving deltas: 100% (261/261), done.
====>> cp bugfix.patch ybc
#!/bin/bash -eo pipefail
cp bugfix.patch ybc
====>> git apply --ignore-space-change --ignore-whitespace bugfix.patch
#!/bin/bash -eo pipefail git apply --ignore-space-change --ignore-whitespace bugfix.patch
====>> wget -qO- https://github.com/thedodd/trunk/releases/download/v0.15.0/trunk-x86_64-unknown-linux-gnu.tar.gz | tar -xzf-
#!/bin/bash -eo pipefail wget -qO- https://github.com/thedodd/trunk/releases/download/v0.15.0/trunk-x86_64-unknown-linux-gnu.tar.gz | tar -xzf-
====>> ./trunk build --release
#!/bin/bash -eo pipefail ./trunk build --release
2022-05-22T00:41:03.683341Z INFO starting build
2022-05-22T00:41:03.683539Z INFO spawning asset pipelines
2022-05-22T00:41:48.880700Z INFO building fromkos
2022-05-22T00:41:48.880700Z INFO building fromkos
2022-05-22T00:41:48.881105Z INFO copying directory path="bs_pub"
2022-05-22T00:41:48.881901Z INFO finished copying directory path="bs_pub"
Blocking waiting for file lock on package cache
Blocking waiting for file lock on package cache
Blocking waiting for file lock on package cache
Blocking waiting for file lock on package cache
Blocking waiting for file lock on package cache
Blocking waiting for file lock on package cache
error: no bin target named worker
error: no bin target named app
2022-05-22T00:41:49.787179Z ERROR error
error from HTML pipeline
Caused by: 0: error from asset pipeline 1: error during cargo build execution 2: cargo call returned a bad status Error: error from HTML pipeline
Caused by: 0: error from asset pipeline 1: error during cargo build execution 2: cargo call returned a bad status Error: Exited with code exit status 1
Step failed Error: runner failed (exited with 101) Task failed Error: task failed
My guess is that you're missing one of Trunk's dependencies, such as wasm-bindgen.
I didn't miss any dependency. Why can I build on my local Ubuntu via the same Dockefile? The problem is build system lacks the libraries required to build Rust-based projects...
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue was closed because it has been stalled for 5 days with no activity.