TESTING SCCACHE

[bjoernQ]

Thank you for your contribution!

We appreciate the time and effort you've put into this pull request.
To help us review it efficiently, please ensure you've gone through the following checklist:

Submission Checklist 📝

• I have updated existing examples or added new ones (if applicable).
• I have used cargo xtask fmt-packages command to ensure that all changed code is formatted correctly.
• My changes were added to the CHANGELOG.md in the proper section.
• I have added necessary changes to user code to the Migration Guide.
• My changes are in accordance to the esp-rs API guidelines

Extra:

• I have read the CONTRIBUTING.md guide and followed its instructions.

Pull Request Details 📖

Description

Please provide a clear and concise description of your changes, including the motivation behind these changes. The context is crucial for the reviewers.

Testing

Describe how you tested your changes.

[MabezDev]

We might need to clear the current caches to "make room" for the sscache stuff? iirc the last time I looked at the runner caches they were full.

[jessebraham]

Do we need both sccache-cache and rust-cache?

[bjoernQ]

we don't need sccache at all since it doesn't give any benefits in our setup (will write another comment why) - and I'm not sure if we really benefit from rust-cache as is either

[bjoernQ]

so ..... sccache won't cache (well it caches but won't hit the cache) if there is a crate with a dependency on any proc-macro-crate (probably transitive)

I guess it makes sense since a proc-macro could do anything but even something like the document-features crate will make sccache ineffective (and we use a lot of proc-macros and so do all the heavier crates we use)

closing this experiment - maybe will do another experiment however