8000 Upgrade sccache to v0.10.0 in upstream docker image by clee2000 · Pull Request #9102 · pytorch/xla · GitHub
[go: up one dir, main page]

Skip to content

Upgrade sccache to v0.10.0 in upstream docker image #9102

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

Merged
merged 4 commits into from
May 8, 2025

Conversation

clee2000
Copy link
Contributor
@clee2000 clee2000 commented May 6, 2025

pytorch/pytorch has started using the original sccache repo instead of our fork, so switch xla to do this too

The fork is really old, and (I think) had changes to enable sccache with nvcc but upstream sccache handles nvcc now. nvcc is also not relevant for the pytorch xla build/test CI. It is also having trouble writing to s3 so there are no cache hits, meaning the build in pytorch/pytorch CI takes >1 hr

@bhavya01 bhavya01 merged commit 5e723de into pytorch:master May 8, 2025
24 checks passed
pytorchmergebot pushed a commit to pytorch/pytorch that referenced this pull request May 8, 2025
The edited comment should have the info.  The code change looks large, but its copied from the install_cache script that our docker images use https://github.com/pytorch/pytorch/blob/6a8006472e431f872ca40c7aad250b61105de583/.ci/docker/common/install_cache.sh#L42

Sccache stopped working on xla at some point near dec 17 2023.  I am not sure what commit caused it.  I think it was having trouble writing to the cache.

Either way, there is an sccache already installed on the docker image, so we should use that instead of a binary from s3 which we're probably no longer sure where it came from/what commit it was built from

The one in the docker image is installed here https://github.com/pytorch/xla/blob/69d438ee65cc250c974ca80edd80462ffbb2e163/.github/upstream/Dockerfile#L61 and is also very old, so I have pytorch/xla#9102 to update it

sccache still not writing properly, i will investigate, but xla build currently broken after the above xla pr, and this should fix it
Pull Request resolved: #153002
Approved by: https://github.com/malfet
zhanyong-wan pushed a commit to zhanyong-wan/pytorch-xla that referenced this pull request May 9, 2025
pytorchbot pushed a commit to pytorch/pytorch that referenced this pull request May 20, 2025
The edited comment should have the info.  The code change looks large, but its copied from the install_cache script that our docker images use https://github.com/pytorch/pytorch/blob/6a8006472e431f872ca40c7aad250b61105de583/.ci/docker/common/install_cache.sh#L42

Sccache stopped working on xla at some point near dec 17 2023.  I am not sure what commit caused it.  I think it was having trouble writing to the cache.

Either way, there is an sccache already installed on the docker image, so we should use that instead of a binary from s3 which we're probably no longer sure where it came from/what commit it was built from

The one in the docker image is installed here https://github.com/pytorch/xla/blob/69d438ee65cc250c974ca80edd80462ffbb2e163/.github/upstream/Dockerfile#L61 and is also very old, so I have pytorch/xla#9102 to update it

sccache still not writing properly, i will investigate, but xla build currently broken after the above xla pr, and this should fix it
Pull Request resolved: #153002
Approved by: https://github.com/malfet

(cherry picked from commit cbcb57d)
atalman pushed a commit to pytorch/pytorch that referenced this pull request May 21, 2025
[CI] Use sccache installed in docker image in xla build (#153002)

The edited comment should have the info.  The code change looks large, but its copied from the install_cache script that our docker images use https://github.com/pytorch/pytorch/blob/6a8006472e431f872ca40c7aad250b61105de583/.ci/docker/common/install_cache.sh#L42

Sccache stopped working on xla at some point near dec 17 2023.  I am not sure what commit caused it.  I think it was having trouble writing to the cache.

Either way, there is an sccache already installed on the docker image, so we should use that instead of a binary from s3 which we're probably no longer sure where it came from/what commit it was built from

The one in the docker image is installed here https://github.com/pytorch/xla/blob/69d438ee65cc250c974ca80edd80462ffbb2e163/.github/upstream/Dockerfile#L61 and is also very old, so I have pytorch/xla#9102 to update it

sccache still not writing properly, i will investigate, but xla build currently broken after the above xla pr, and this should fix it
Pull Request resolved: #153002
Approved by: https://github.com/malfet

(cherry picked from commit cbcb57d)

Co-authored-by: Catherine Lee <csl@fb.com>
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 this pull request may close these issues.

2 participants
0