Does arch get included in the cache key?

[max-sixty]

Thanks a lot for offering this, I've found it the simplest and best way to get crates installed!

---

We've recently started seeing some failures in our jobs. We run jobs on both macos-14, which using aarch64 and macos-latest, which uses x86. (So 14 is actually more recent than latest...)

It looks like the cache key is the same for both, even though the binaries aren't compatible:

• macos-14 job: key: cargo-install-cargo-insta-1.38.0-a4f6b43f6bcdf44918ef
• macos-latest job: key: cargo-install-cargo-insta-1.38.0-a4f6b43f6bcdf44918ef

We then get an error Bad CPU type in executable (os error 86), ref PRQL/prql#4362

It looks like this should be covered by #20; any ideas why the key seems to be the same?

[baptiste0928]

Thanks for reporting this, the os version wasn't being run on mac because I was checking the os name against MacOS instead of macOS ( 😅 ). I fixed this and also included the os arch explicitly in the cache key.

I will publish a new version with these fixes.

[max-sixty]

Thanks @baptiste0928 !