Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI (sometimes) fails on macOS #180

Closed
johan-bjareholt opened this issue Oct 29, 2020 · 5 comments · Fixed by #193
Closed

CI (sometimes) fails on macOS #180

johan-bjareholt opened this issue Oct 29, 2020 · 5 comments · Fixed by #193

Comments

@johan-bjareholt
Copy link
Member

Sometimes it's this

 error[E0463]: can't find crate for `pear_codegen` which `pear` depends on
  --> /Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/rocket_http-0.4.5/src/lib.rs:15:14
   |
15 | #[macro_use] extern crate pear;
   |              ^^^^^^^^^^^^^^^^^^ can't find crate

error: aborting due to previous error

For more information about this error, try `rustc --explain E0463`.
error: could not compile `rocket_http`

While other times it's a similar thing but it can't find serde_derive or serde or whatever. I have no idea why and it's even more strange that it only occurs on macOS as it doesn't seem to have to do with anything platform specific.

@johan-bjareholt johan-bjareholt changed the title CI fails on macOS CI (sometimes) fails on macOS Oct 29, 2020
@ErikBjare
Copy link
Member

Happened in the bundle repo too just now. Weird af.

@ErikBjare
Copy link
Member

ErikBjare commented Dec 28, 2020

@johan-bjareholt I have a theory of what might cause this.

IME, the issue rarely occurs when there has been a recent update to the Cargo.lock (flushing the cache), then things start to fail when there is a new Rust nightly. This suggests that it might be due to the stale build cache (as previously suspected) that somehow doesn't get updated for the new nightly.

Does that sound like a possible cause to you?

Edit: lol, just realized I said the exact same thing in #192 (comment), with proof.

@ErikBjare
Copy link
Member

Still getting this: https://github.com/ActivityWatch/activitywatch/runs/1618609088#step:11:498

Perhaps we should just turn off the Cargo cache entirely for now.

@ErikBjare ErikBjare reopened this Dec 30, 2020
ErikBjare added a commit to ActivityWatch/activitywatch that referenced this issue Dec 30, 2020
@ErikBjare
Copy link
Member

ErikBjare commented Dec 30, 2020

I disabled the Cargo cache for macOS and it seems to work. Hopefully, it stays that way.

Not too big a sacrifice to keep the cache off specifically for macOS builds if it stops the builds from failing intermittently.

@ErikBjare
Copy link
Member

Tried enabling it again, but spuriously getting weird stuff: https://github.com/ActivityWatch/activitywatch/runs/7340434809

   Compiling aw-transform v0.1.0 (/Users/runner/work/activitywatch/activitywatch/aw-server-rust/aw-transform)
error[E0786]: found invalid metadata files for crate `rocket_codegen` which `rocket` depends on
  --> aw-transform/src/split_url.rs:25:9
   |
25 |     use rocket::http::uri::Absolute;
   |         ^^^^^^
   |
   = note: invalid metadata version found: /Users/runner/work/activitywatch/activitywatch/aw-server-rust/target/release/deps/librocket_codegen-66a6ea628577ce59.dylib

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants