Skip to content

[ci] move sccache stats off RDS#79366

Closed
suo wants to merge 9 commits intogh/suo/557/basefrom
gh/suo/557/head
Closed

[ci] move sccache stats off RDS#79366
suo wants to merge 9 commits intogh/suo/557/basefrom
gh/suo/557/head

Conversation

We want to decommission RDS, so upload sccache stats to S3/GHA as
appropriate.

[ghstack-poisoned]
@facebook-github-bot
Copy link
Copy Markdown
Contributor

facebook-github-bot commented Jun 12, 2022

🔗 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.

Click here to manually regenerate this comment.

@suo suo added the ciflow/trunk Trigger trunk jobs on your pull request label Jun 12, 2022
We want to decommission RDS, so upload sccache stats to S3/GHA as
appropriate.

[ghstack-poisoned]
suo added a commit that referenced this pull request Jun 12, 2022
We want to decommission RDS, so upload sccache stats to S3/GHA as
appropriate.

ghstack-source-id: 238ab57
Pull Request resolved: #79366
We want to decommission RDS, so upload sccache stats to S3/GHA as
appropriate.

[ghstack-poisoned]
suo added a commit that referenced this pull request Jun 12, 2022
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]
suo added a commit that referenced this pull request Jun 12, 2022
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]
suo added a commit that referenced this pull request Jun 12, 2022
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]
suo added a commit that referenced this pull request Jun 12, 2022
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]
suo added a commit that referenced this pull request Jun 12, 2022
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]
suo added a commit that referenced this pull request Jun 12, 2022
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]
suo added a commit that referenced this pull request Jun 12, 2022
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-source-id: a1f9fcb
Pull Request resolved: #79370
We want to decommission RDS, so upload sccache stats to S3/GHA as
appropriate.

[ghstack-poisoned]
suo added a commit that referenced this pull request Jun 12, 2022
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]
suo added a commit that referenced this pull request Jun 12, 2022
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]
suo added a commit that referenced this pull request Jun 12, 2022
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]
suo added a commit that referenced this pull request Jun 12, 2022
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]
suo added a commit that referenced this pull request Jun 12, 2022
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-source-id: 2654da6
Pull Request resolved: #79370
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 }}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

is the OUR_ just to not collide with GITHUB_JOB_ID which we know is not what we care about?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

can't decide if we should add a comment to clarify that

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

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 = {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

we probably can just make this code more generic, I can take it as a followup

@suo
Copy link
Copy Markdown
Member Author

suo commented Jun 13, 2022

@pytorchbot merge

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

@pytorchbot successfully started a merge job. Check the current status here

@github-actions
Copy link
Copy Markdown
Contributor

Hey @suo.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

suo added a commit that referenced this pull request Jun 13, 2022
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]
suo added a commit that referenced this pull request Jun 13, 2022
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]
pytorchmergebot pushed a commit that referenced this pull request Jun 13, 2022
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
pytorchmergebot pushed a commit that referenced this pull request Jun 14, 2022
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
facebook-github-bot pushed a commit that referenced this pull request Jun 14, 2022
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
facebook-github-bot pushed a commit that referenced this pull request Jun 15, 2022
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
facebook-github-bot pushed a commit that referenced this pull request Jun 16, 2022
…) (#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
@facebook-github-bot facebook-github-bot deleted the gh/suo/557/head branch June 17, 2022 14:17
laurentdupin pushed a commit to laurentdupin/pytorch that referenced this pull request Apr 25, 2026
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
laurentdupin pushed a commit to laurentdupin/pytorch that referenced this pull request Apr 25, 2026
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
laurentdupin pushed a commit to laurentdupin/pytorch that referenced this pull request Apr 25, 2026
…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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/trunk Trigger trunk jobs on your pull request cla signed Merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants