-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[docs] Sccache bug has been fixed #40873
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
Conversation
We are still seeing instances of this in |
I just did an incremental build of the Swift compiler using Ninja and it was definitely faster the second time. |
Try running
|
I just compiled the Swift toolchain and it took a few minutes (it was an incremental build with no changes). I ran
Next, I'll modify a source code file and see if anything pops up. I did NOT set the max cache size to 10 GiB when starting the server; I set it to 50 GiB. |
I got the following after slightly modifying one C++ file and rebuilding:
|
So then it seems that this isn't fixed. Looks like @ahoppen got some code in to improve the situation, but it missed the tag by two months 😞 |
The sccache issue actually still exists in 0.2.15. mozilla/sccache#898 is the PR that introduced the issue and I submitted mozilla/sccache#959 to fix the issue introduced by that PR. However, sccache hasn’t release a new version since. Regarding gcc vs. clang: I’m no sccache expert but I believe that gcc and clang have sufficiently similar compiler arguments that sccache can use the same rules to determine whether a particular compiler invocation can be cached. |
sccache release 0.3.0 version which include the fix PR. |
If this is an external dependency that people download separately from the Swift compiler, then people might already be using the new Sccache with the bug fix. We need to have someone validate that the newer version is being used. |
I would like to hold this until |
|
I have set up notifications so that I’ll be pinged when that PR is merged. Then we should be able to get this reviewed. |
@CodaFi please review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified that version 0.3.0 of sccache installed via homebrew correctly caches compilation commands again.
@swift-ci Please smoke test |
In v2.15.0, the target duplication problem has supposedly been addressed. I have not verified it's actually fixed because I haven't built Swift from source yet. Here is the sequence of events surrounding the fix:
GettingStarted.md
, is merged and creates the bug:GettingStarted.md
remains.I have one question though: the commit goes to the file
gcc.rs
, yet (based on my limited and likely flawed understanding) Clang is often used for Swift instead of GCC. Does that mean the patch fixes builds using GCC, but Clang builds are still broken? For reference, I plan to use Xcode instead of Ninja to build the Swift compiler from source, and am still reading the beginner documentation on how to do it.