Skip to content

Conversation

@xuzhao9
Copy link
Contributor

@xuzhao9 xuzhao9 commented Sep 8, 2022

Upload the benchmark result to S3 and make it accessible to the public.

The URL is available at the end of the "Upload to S3" step of the workflow. For example, this PR uploads 3 files:

Uploaded the result file control.json to https://ossci-metrics.s3.amazonaws.com/torchbench-pr-test/pr84726/control.json
Uploading file treatment.json to S3 with key: torchbench-pr-test/pr84726/treatment.json
Uploaded the result file treatment.json to https://ossci-metrics.s3.amazonaws.com/torchbench-pr-test/pr84726/treatment.json
Uploading file result.csv to S3 with key: torchbench-pr-test/pr84726/result.csv
Uploaded the result file result.csv to https://ossci-metrics.s3.amazonaws.com/torchbench-pr-test/pr84726/result.csv

RUN_TORCHBENCH: nvfuser

@xuzhao9 xuzhao9 requested a review from a team as a code owner September 8, 2022 23:20
@pytorch-bot
Copy link

pytorch-bot bot commented Sep 8, 2022

🔗 Helpful Links

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

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

✅ No Failures, 1 Pending

As of commit 87bf26e:
💚 Looks good so far! There are no failures yet. 💚

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

@pytorch-bot pytorch-bot bot added the release notes: releng release notes category label Sep 8, 2022
Copy link
Contributor

@davidberard98 davidberard98 left a comment

Choose a reason for hiding this comment

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

Just had one question, otherwise LGTM! Thanks for this 😄

def upload_file(self, file_path: Path, filekey_prefix: str) -> None:
assert file_path.is_file(), f"Specified file path {file_path} does not exist or not file."
file_name = file_path.name
s3_key = f"{self.prefix}/{filekey_prefix}/{file_name}"
Copy link
Contributor

Choose a reason for hiding this comment

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

Is filekey_prefix unique or would it could repeated over multiple runs of the same PR or the same git commit?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It is the same for the same PR, the second run will overwrite the result of the first run.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Let me know if you need to keep the run history. If you do, we probably can do it in a follow-up PR.

@xuzhao9
Copy link
Contributor Author

xuzhao9 commented Sep 9, 2022

@pytorchbot -g merge

@pytorch-bot
Copy link

pytorch-bot bot commented Sep 9, 2022

❌ 🤖 pytorchbot command failed:

@pytorchbot: error: unrecognized arguments: -g

usage: @pytorchbot [-h] {merge,revert,rebase,label} ...

Try @pytorchbot --help for more info.

@xuzhao9
Copy link
Contributor Author

xuzhao9 commented Sep 9, 2022

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

@pytorchbot successfully started a merge job. Check the current status here.
The merge job was triggered without a flag. This means that your change will be merged once all checks on your PR have passed (ETA: 0-4 Hours). If this is not the intended behavior, feel free to use some of the other merge options in the wiki.
Please reach out to the PyTorch DevX Team with feedback or questions!

@github-actions
Copy link
Contributor

github-actions bot commented Sep 9, 2022

Hey @xuzhao9.
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.

@xuzhao9 xuzhao9 deleted the xz9/upload-pr-ci-s3 branch September 9, 2022 22:54
facebook-github-bot pushed a commit that referenced this pull request Sep 11, 2022
Summary:
Upload the benchmark result to S3 and make it accessible to the public.

The URL is available at the end of the "Upload to S3" step of the workflow. For example, this PR uploads 3 files:
```
Uploaded the result file control.json to https://ossci-metrics.s3.amazonaws.com/torchbench-pr-test/pr84726/control.json
Uploading file treatment.json to S3 with key: torchbench-pr-test/pr84726/treatment.json
Uploaded the result file treatment.json to https://ossci-metrics.s3.amazonaws.com/torchbench-pr-test/pr84726/treatment.json
Uploading file result.csv to S3 with key: torchbench-pr-test/pr84726/result.csv
Uploaded the result file result.csv to https://ossci-metrics.s3.amazonaws.com/torchbench-pr-test/pr84726/result.csv
```

RUN_TORCHBENCH: nvfuser

Pull Request resolved: #84726
Approved by: https://github.com/davidberard98

Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/cd50512d414e352fb9088805d8d66bf6880895d1

Reviewed By: izaitsevfb

Differential Revision: D39407102

Pulled By: xuzhao9

fbshipit-source-id: 163a916b4cdb1ae768be6f55a1bf3d41c4660462
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.

4 participants