mirror of
https://github.com/denoland/rusty_v8.git
synced 2025-01-11 08:34:01 -05:00
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 https://github.com/actions-rs/cargo/issues/111.
This commit is contained in:
parent
fdc03238c4
commit
ac9bb44e33
1 changed files with 0 additions and 9 deletions
9
.github/workflows/ci.yml
vendored
9
.github/workflows/ci.yml
vendored
|
@ -98,14 +98,6 @@ jobs:
|
|||
echo "::set-env name=CARGO_TARGET_AARCH64_UNKNOWN_LINUX_GNU_LINKER::/usr/bin/aarch64-linux-gnu-gcc-5"
|
||||
echo "::set-env name=QEMU_LD_PREFIX::/usr/aarch64-linux-gnu"
|
||||
|
||||
- name: Configure cargo data directory
|
||||
# After this point, all cargo registry and crate data is stored in
|
||||
# $GITHUB_WORKSPACE/target/cargo. This allows us to cache only the files
|
||||
# that are needed during the build process. Additionally, this works
|
||||
# around a bug in the 'cache' action that causes directories outside of
|
||||
# the workspace dir to be saved/restored incorrectly.
|
||||
run: echo "::set-env name=CARGO_HOME::$(pwd)/target/cargo"
|
||||
|
||||
- name: Cache
|
||||
uses: actions/cache@v2
|
||||
with:
|
||||
|
@ -116,7 +108,6 @@ jobs:
|
|||
# come from the registry. By additionally saving the sccache cache
|
||||
# directory it's still possible to build v8 fast.
|
||||
path: |-
|
||||
target/cargo
|
||||
target/sccache
|
||||
target/*/.*
|
||||
target/*/build
|
||||
|
|
Loading…
Reference in a new issue