Skip to content

[CI] Use sccache installed in docker image in xla build#153002

Closed
clee2000 wants to merge 4 commits intomainfrom
csl/xla_sccache
Closed

[CI] Use sccache installed in docker image in xla build#153002
clee2000 wants to merge 4 commits intomainfrom
csl/xla_sccache

Conversation

@clee2000
Copy link
Contributor

@clee2000 clee2000 commented May 6, 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

function write_sccache_stub() {

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

@pytorch-bot
Copy link

pytorch-bot bot commented May 6, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/153002

Note: Links to docs will display an error until the docs builds have been completed.

❌ 1 New Failure, 18 Cancelled Jobs, 2 Unrelated Failures

As of commit 7be1f26 with merge base 5fe58ab (image):

NEW FAILURE - The following job has failed:

CANCELLED JOBS - The following jobs were cancelled. Please retry:

UNSTABLE - The following jobs are marked as unstable, possibly due to flakiness on trunk:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@clee2000 clee2000 added the topic: not user facing topic category label May 6, 2025
@clee2000 clee2000 marked this pull request as ready for review May 7, 2025 20:08
@clee2000 clee2000 requested a review from a team as a code owner May 7, 2025 20:08
Copy link
Contributor

@malfet malfet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure

@malfet
Copy link
Contributor

malfet commented May 8, 2025

@pytorchbot merge -f "Sparta!!! (i.e. let's test in trunk)"

@clee2000
Copy link
Contributor Author

clee2000 commented May 8, 2025

@pytorchbot merge -f "should be fine, xla is fine and I checked that the docker digest is the new one, canceled jobs are dup pull jobs"

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@atalman
Copy link
Contributor

atalman commented May 20, 2025

@pytorchbot cherry-pick --onto release/2.7 -c critical

pytorchbot pushed a commit 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)
@pytorchbot
Copy link
Collaborator

Cherry picking #153002

The cherry pick PR is at #153983 and it is recommended to link a critical cherry pick PR with an issue. The following tracker issues are updated:

Details for Dev Infra team Raised by workflow job

atalman pushed a commit 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>
@github-actions github-actions bot deleted the csl/xla_sccache branch June 21, 2025 02:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants