This repository has been archived by the owner on Oct 13, 2023. It is now read-only.
Cargo builds on macOS runners have ephemeral failures #111
Comments
|
I'm experiencing the same issue, also on macOS. |
piscisaureus
added a commit
to denoland/rusty_v8
that referenced
this issue
Aug 27, 2020
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.
piscisaureus
added a commit
to denoland/rusty_v8
that referenced
this issue
Aug 27, 2020
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.
piscisaureus
added a commit
to denoland/rusty_v8
that referenced
this issue
Aug 27, 2020
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.
|
We're having the same problem here for macOS runners: https://github.com/terrabasedb/terrabase/runs/1055128389#step:7:86 |
This was referenced Sep 2, 2020
|
Same, on https://github.com/deltachat/deltachat-core-rust/ it randomly fails with |
This was referenced Oct 23, 2020
jdno
added a commit
to playlunaria/lunaria
that referenced
this issue
Nov 3, 2020
We are experiencing intermittent build failures on macOS in preview builds. Similar issues have been reported by others maintainers before, and a good summary of the issue can be found in the actions-rs/cargo repository [1]. [1]: actions-rs/cargo#111
jdno
added a commit
to playlunaria/lunaria
that referenced
this issue
Nov 3, 2020
We are experiencing intermittent build failures of macOS builds on GitHub Actions. Similar issues have been reported by others maintainers before, and a good summary of the issue can be found in the actions-rs/cargo repository [1]. As a temporary workaround, caching is disabled for macOS builds. [1]: actions-rs/cargo#111
jdno
added a commit
to playlunaria/lunaria
that referenced
this issue
Nov 3, 2020
We are experiencing intermittent build failures of macOS builds on GitHub Actions. Similar issues have been reported by others maintainers before, and a good summary of the issue can be found in the actions-rs/cargo repository [1]. As a temporary workaround, caching is disabled for macOS builds. [1]: actions-rs/cargo#111
|
Common conclusion is that it is related to caching (also helped me with the same problem). |
|
I think we're encountering this too with https://github.com/imazen/imageflow We have a large build and caching is really important. Has anyone figured out how to fix it? |
|
It sounds like this is related to needing GNU tar instead of BSD tar on OS X- actions/cache#403 |
ianoc
added a commit
to ianoc/fuser
that referenced
this issue
Feb 27, 2021
It seems this is a common/known issue thats being worked on to do with github actions/cache on macOS actions-rs/cargo#111
cberner
pushed a commit
to cberner/fuser
that referenced
this issue
Feb 27, 2021
It seems this is a common/known issue thats being worked on to do with github actions/cache on macOS actions-rs/cargo#111
ry
added a commit
to denoland/deno
that referenced
this issue
Mar 13, 2021
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.
ry
added a commit
to denoland/deno
that referenced
this issue
Mar 13, 2021
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.
ry
added a commit
to denoland/deno
that referenced
this issue
Mar 13, 2021
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.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a question about running Cargo builds on macOS, and I was wondering if someone might know the answer.
We've been experience flaky builds (unicode-org/icu4x#201) caused by ephemeral build errors that appear to have started showing up all of a sudden on a few PRs.
The error message in the log mentions
error[E0463]: can't find crate for serde_derive which serde depends on, and when I looked through serde-rs/serde#856 and similar issues (and verified the transitive dependencies' versions of serde used, usingcargo-tree), I don't see the same serde version conflict problems that were described. And either way, I don't think that would explain the ephemeral nature.One possible theory is that it might relate to this issue from 3 years ago of cargo build failing on macOS due to linking issues when dependencies are added (rust-lang/cargo#4775). I don't know if that is still relevant to cargo builds. The GH builds that use the GH caching action (thereby retrieving cargo crate cache) are the ones that seem to fail ephemerally (ex1, ex2). The tests run after I turned off the GH caching action seem to pass (ex1, ex2). And FWIW, in my personal fork, even when I leave the GH cache action on, the builds pass (ex1, ex2).
Any pointers or suggestions would be appreciated, thanks.
The text was updated successfully, but these errors were encountered: