Skip to content

Commit 8e35aaf

Browse files
committed
ci: don't store $CARGO_HOME in Github Actions cache (#443)
There currently is a problem related to Github Actions in general or the 'actions-rs/cargo' action in particular, which causes cargo to be unable to find the 'serde_derive' crate when the cargo home dir has been restored from cache. This issue is also being reported by others, e.g. at actions-rs/cargo#111.
1 parent d907422 commit 8e35aaf

File tree

1 file changed

+0
-9
lines changed

1 file changed

+0
-9
lines changed

.github/workflows/ci.yml

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -98,14 +98,6 @@ jobs:
9898
echo "::set-env name=CARGO_TARGET_AARCH64_UNKNOWN_LINUX_GNU_LINKER::/usr/bin/aarch64-linux-gnu-gcc-5"
9999
echo "::set-env name=QEMU_LD_PREFIX::/usr/aarch64-linux-gnu"
100100
101-
- name: Configure cargo data directory
102-
# After this point, all cargo registry and crate data is stored in
103-
# $GITHUB_WORKSPACE/target/cargo. This allows us to cache only the files
104-
# that are needed during the build process. Additionally, this works
105-
# around a bug in the 'cache' action that causes directories outside of
106-
# the workspace dir to be saved/restored incorrectly.
107-
run: echo "::set-env name=CARGO_HOME::$(pwd)/target/cargo"
108-
109101
- name: Cache
110102
uses: actions/cache@v2
111103
with:
@@ -116,7 +108,6 @@ jobs:
116108
# come from the registry. By additionally saving the sccache cache
117109
# directory it's still possible to build v8 fast.
118110
path: |-
119-
target/cargo
120111
target/sccache
121112
target/*/.*
122113
target/*/build

0 commit comments

Comments
 (0)