[ci] move sccache stats off RDS#79366
Conversation
We want to decommission RDS, so upload sccache stats to S3/GHA as appropriate. [ghstack-poisoned]
🔗 Helpful links
✅ No Failures (0 Pending)As of commit b39b476 (more details on the Dr. CI page): Expand to see more💚 💚 Looks good so far! There are no failures yet. 💚 💚 This comment was automatically generated by Dr. CI (expand for details).Please report bugs/suggestions to the (internal) Dr. CI Users group. |
We want to decommission RDS, so upload sccache stats to S3/GHA as appropriate. [ghstack-poisoned]
We want to decommission RDS, so upload sccache stats to S3/GHA as appropriate. [ghstack-poisoned]
With #79366, the only remaining use case for RDS is import latency stats. Afaik we do not look at these, so removing, which eliminates our last dependency on RDS. [ghstack-poisoned]
We want to decommission RDS, so upload sccache stats to S3/GHA as appropriate. [ghstack-poisoned]
With #79366, the only remaining use case for RDS is import latency stats. Afaik we do not look at these, so removing, which eliminates our last dependency on RDS. [ghstack-poisoned]
With #79366, the only remaining use case for RDS is import latency stats. Afaik we do not look at these, so removing, which eliminates our last dependency on RDS. [ghstack-poisoned]
We want to decommission RDS, so upload sccache stats to S3/GHA as appropriate. [ghstack-poisoned]
With #79366, the only remaining use case for RDS is import latency stats. Afaik we do not look at these, so removing, which eliminates our last dependency on RDS. [ghstack-poisoned]
With #79366, the only remaining use case for RDS is import latency stats. Afaik we do not look at these, so removing, which eliminates our last dependency on RDS. [ghstack-poisoned]
We want to decommission RDS, so upload sccache stats to S3/GHA as appropriate. [ghstack-poisoned]
With #79366, the only remaining use case for RDS is import latency stats. Afaik we do not look at these, so removing, which eliminates our last dependency on RDS. [ghstack-poisoned]
We want to decommission RDS, so upload sccache stats to S3/GHA as appropriate. [ghstack-poisoned]
With #79366, the only remaining use case for RDS is import latency stats. Afaik we do not look at these, so removing, which eliminates our last dependency on RDS. [ghstack-poisoned]
With #79366, the only remaining use case for RDS is import latency stats. Afaik we do not look at these, so removing, which eliminates our last dependency on RDS. [ghstack-poisoned]
We want to decommission RDS, so upload sccache stats to S3/GHA as appropriate. [ghstack-poisoned]
With #79366, the only remaining use case for RDS is import latency stats. Afaik we do not look at these, so removing, which eliminates our last dependency on RDS. [ghstack-poisoned]
With #79366, the only remaining use case for RDS is import latency stats. Afaik we do not look at these, so removing, which eliminates our last dependency on RDS. [ghstack-poisoned]
| PR_LABELS: ${{ toJson(github.event.pull_request.labels.*.name) }} | ||
| TORCH_CUDA_ARCH_LIST: 5.2 | ||
| DOCKER_IMAGE: ${{ steps.calculate-docker-image.outputs.docker-image }} | ||
| OUR_GITHUB_JOB_ID: ${{ steps.get-job-id.outputs.job-id }} |
There was a problem hiding this comment.
is the OUR_ just to not collide with GITHUB_JOB_ID which we know is not what we care about?
There was a problem hiding this comment.
can't decide if we should add a comment to clarify that
There was a problem hiding this comment.
Yeah, just in general we shouldn't trample on the GITHUB_ prefix because GITHUB may add env vars in the future
| return name.replace(" ", "_").replace("-", "_").lower() | ||
|
|
||
|
|
||
| STAT_NAMES = { |
There was a problem hiding this comment.
what happens if these names change sometime in the future (which is probably rare)? will we rely on alerts on the data in rockset to ensure reporting stability here?
There was a problem hiding this comment.
we probably can just make this code more generic, I can take it as a followup
|
@pytorchbot merge |
|
@pytorchbot successfully started a merge job. Check the current status here |
|
Hey @suo. |
With #79366, the only remaining use case for RDS is import latency stats. Afaik we do not look at these, so removing, which eliminates our last dependency on RDS. [ghstack-poisoned]
With #79366, the only remaining use case for RDS is import latency stats. Afaik we do not look at these, so removing, which eliminates our last dependency on RDS. [ghstack-poisoned]
With #79366, the only remaining use case for RDS is import latency stats. Afaik we do not look at these, so removing, which eliminates our last dependency on RDS. Pull Request resolved: #79370 Approved by: https://github.com/janeyx99
Allows use of .jenkins/pytorch/build.sh without assuming OUR_GITHUB_JOB_ID is set. This is a regression caused by #79366. Pull Request resolved: #79541 Approved by: https://github.com/suo, https://github.com/seemethere
Summary: We want to decommission RDS, so upload sccache stats to S3/GHA as appropriate. Pull Request resolved: #79366 Approved by: https://github.com/janeyx99 Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/3771331b2a692399c228ce0aa2290a9b03010018 Reviewed By: osalpekar Differential Revision: D37119148 Pulled By: suo fbshipit-source-id: 0000b03cbc8eabc8acc16da5d38b1764e8e8cab9
Summary: With #79366, the only remaining use case for RDS is import latency stats. Afaik we do not look at these, so removing, which eliminates our last dependency on RDS. Pull Request resolved: #79370 Approved by: https://github.com/janeyx99 Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/964d5059587c017b02f1d7d62587722a38683c63 Reviewed By: malfet Differential Revision: D37153120 Pulled By: suo fbshipit-source-id: 6a2e1fb827a88e0828b1f05fdbe62f07ec61da87
…) (#79541) Summary: Allows use of .jenkins/pytorch/build.sh without assuming OUR_GITHUB_JOB_ID is set. This is a regression caused by #79366. Pull Request resolved: #79541 Approved by: https://github.com/suo, https://github.com/seemethere Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/adaafeedb1f66c4c877a446a6082f2a761878883 Reviewed By: malfet Differential Revision: D37156933 fbshipit-source-id: a9309facfccfb8b4aa4f8fb7a727929fe760d95c
We want to decommission RDS, so upload sccache stats to S3/GHA as appropriate. Pull Request resolved: pytorch#79366 Approved by: https://github.com/janeyx99
With pytorch#79366, the only remaining use case for RDS is import latency stats. Afaik we do not look at these, so removing, which eliminates our last dependency on RDS. Pull Request resolved: pytorch#79370 Approved by: https://github.com/janeyx99
…rch#79541) Allows use of .jenkins/pytorch/build.sh without assuming OUR_GITHUB_JOB_ID is set. This is a regression caused by pytorch#79366. Pull Request resolved: pytorch#79541 Approved by: https://github.com/suo, https://github.com/seemethere
Stack from ghstack (oldest at bottom):
CUSTOM_TEST_ARTIFACT_BUILD_DIR#79362We want to decommission RDS, so upload sccache stats to S3/GHA as
appropriate.