Skip to content

.github: Add action workflow to update S3 HTMLS #49509

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

.github: Add action workflow to update S3 HTMLS #49509

wants to merge 1 commit into from

Conversation

seemethere
Copy link
Member

@seemethere seemethere commented Dec 16, 2020 •
edited
Loading

Successful run: https://github.com/pytorch/pytorch/runs/1572315901

Signed-off-by: Eli Uriegas eliuriegas@fb.com

@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Dec 16, 2020 •
edited
Loading

💊 CI failures summary and remediations

As of commit dc1d3c5 (more details on the Dr. CI page):

  • 4/4 failures introduced in this PR

🕵️ 4 new failures recognized by patterns

The following CI failures do not appear to be due to upstream breakages:

See CircleCI build pytorch_xla_linux_bionic_py3_6_clang9_build (1/4)

Step: "(Optional) Merge target branch" (full log | diagnosis details | 🔁 rerun)

Automatic merge failed; fix conflicts and then commit the result. 
CONFLICT (add/add): Merge conflict in .circleci/scripts/windows_cuda_install.sh
Auto-merging .circleci/scripts/windows_cuda_install.sh
CONFLICT (add/add): Merge conflict in .circleci/scripts/binary_linux_test.sh
Auto-merging .circleci/scripts/binary_linux_test.sh
CONFLICT (add/add): Merge conflict in .circleci/config.yml
Auto-merging .circleci/config.yml
CONFLICT (add/add): Merge conflict in .circleci/cimodel/data/windows_build_definitions.py
Auto-merging .circleci/cimodel/data/windows_build_definitions.py
CONFLICT (add/add): Merge conflict in .circleci/cimodel/data/simple/util/versions.py
Auto-merging .circleci/cimodel/data/simple/util/versions.py
Automatic merge failed; fix conflicts and then commit the result.


Exited with code exit status 1

See CircleCI build pytorch_linux_xenial_py3_clang5_asan_test2 (2/4)

Step: "Run tests" (full log | diagnosis details | 🔁 rerun)

Dec 17 20:52:49 RuntimeError: test_quantization failed! 
Dec 17 20:52:47 Generated XML report: test-reports/dist-gloo/TEST-quantization.test_quantized_tensor.TestQuantizedTensor-20201217201509.xml
Dec 17 20:52:47 Generated XML report: test-reports/dist-gloo/TEST-quantization.test_workflow_module.TestRecordHistogramObserver-20201217201509.xml
Dec 17 20:52:47 Generated XML report: test-reports/dist-gloo/TEST-quantization.test_backward_compatibility.TestSerialization-20201217201509.xml
Dec 17 20:52:47 Generated XML report: test-reports/dist-gloo/TEST-quantization.test_quantized_module.TestStaticQuantizedModule-20201217201509.xml
Dec 17 20:52:47 Generated XML report: test-reports/dist-gloo/TEST-quantization.test_quantized_op.TestQNNPackOps-20201217201509.xml
Dec 17 20:52:49 Traceback (most recent call last):
Dec 17 20:52:49   File "test/run_test.py", line 896, in <module>
Dec 17 20:52:49     main()
Dec 17 20:52:49   File "test/run_test.py", line 879, in main
Dec 17 20:52:49     raise RuntimeError(err_message)
Dec 17 20:52:49 RuntimeError: test_quantization failed!
Dec 17 20:52:49 + cleanup
Dec 17 20:52:49 + retcode=1
Dec 17 20:52:49 + set +x
Dec 17 20:52:49 =================== sccache compilation log ===================
Dec 17 20:52:49 =========== If your build fails, please take a look at the log above for possible reasons ===========
Dec 17 20:52:49 Compile requests                      0
Dec 17 20:52:49 Compile requests executed             0
Dec 17 20:52:49 Cache hits                            0
Dec 17 20:52:49 Cache misses                          0
Dec 17 20:52:49 Cache timeouts                        0

See CircleCI build pytorch_linux_xenial_cuda9_2_cudnn7_py3_gcc5_4_build (3/4)

Step: "(Optional) Merge target branch" (full log | diagnosis details | 🔁 rerun)

Automatic merge failed; fix conflicts and then commit the result. 
CONFLICT (add/add): Merge conflict in .circleci/scripts/windows_cuda_install.sh
Auto-merging .circleci/scripts/windows_cuda_install.sh
CONFLICT (add/add): Merge conflict in .circleci/scripts/binary_linux_test.sh
Auto-merging .circleci/scripts/binary_linux_test.sh
CONFLICT (add/add): Merge conflict in .circleci/config.yml
Auto-merging .circleci/config.yml
CONFLICT (add/add): Merge conflict in .circleci/cimodel/data/windows_build_definitions.py
Auto-merging .circleci/cimodel/data/windows_build_definitions.py
CONFLICT (add/add): Merge conflict in .circleci/cimodel/data/simple/util/versions.py
Auto-merging .circleci/cimodel/data/simple/util/versions.py
Automatic merge failed; fix conflicts and then commit the result.


Exited with code exit status 1

See CircleCI build pytorch_linux_xenial_py3_6_gcc5_4_build (4/4)

Step: "(Optional) Merge target branch" (full log | diagnosis details | 🔁 rerun)

Automatic merge failed; fix conflicts and then commit the result. 
CONFLICT (add/add): Merge conflict in .circleci/scripts/windows_cuda_install.sh
Auto-merging .circleci/scripts/windows_cuda_install.sh
CONFLICT (add/add): Merge conflict in .circleci/scripts/binary_linux_test.sh
Auto-merging .circleci/scripts/binary_linux_test.sh
CONFLICT (add/add): Merge conflict in .circleci/config.yml
Auto-merging .circleci/config.yml
CONFLICT (add/add): Merge conflict in .circleci/cimodel/data/windows_build_definitions.py
Auto-merging .circleci/cimodel/data/windows_build_definitions.py
CONFLICT (add/add): Merge conflict in .circleci/cimodel/data/simple/util/versions.py
Auto-merging .circleci/cimodel/data/simple/util/versions.py
Automatic merge failed; fix conflicts and then commit the result.


Exited with code exit status 1
This comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions to the (internal) Dr. CI Users group.

This comment has been revised 23 times.

@seemethere seemethere force-pushed the seemethere/add_s3_updater_action branch 3 times, most recently from e1e99ff to 20e6225 Compare December 17, 2020 18:37
@seemethere
.github: Add action workflow to update S3 HTMLS
dc1d3c5 
Signed-off-by: Eli Uriegas <eliuriegas@fb.com>
@seemethere seemethere force-pushed the seemethere/add_s3_updater_action branch from 20e6225 to dc1d3c5 Compare December 17, 2020 18:45
@seemethere seemethere requested a review from a team December 17, 2020 18:45
@seemethere seemethere marked this pull request as ready for review December 17, 2020 18:47
walterddr
walterddr approved these changes Dec 17, 2020
View reviewed changes
Copy link
Contributor

@walterddr walterddr left a comment

Choose a reason for hiding this comment

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

gogogo

facebook-github-bot
facebook-github-bot reviewed Dec 17, 2020
View reviewed changes
Copy link
Contributor

@facebook-github-bot facebook-github-bot left a comment

Choose a reason for hiding this comment

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

@seemethere has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

@samestep
Copy link
Contributor

What does this do exactly?

@seemethere
Copy link
Member Author

seemethere commented Dec 17, 2020 •
edited
Loading

It automates the updating of html indices through a docker image that was created as part of pytorch/builder#607

A follow up PR to this will need to be made to disable the current HTML updates, luckily they produce the same output so they can run in tandem for a bit.

@samestep
Copy link
Contributor

It automates the updating of html indices through a docker image that was created as part of pytorch/builder#607

Ah ok; where are these HTML indices? (are they available on the web?)

@seemethere
Copy link
Member Author

It automates the updating of html indices through a docker image that was created as part of pytorch/builder#607

Ah ok; where are these HTML indices? (are they available on the web?)

Yes these are the current html indices that are used for installing pytorch from download.pytorch.org

See https://pytorch.org/get-started

@facebook-github-bot
Copy link
Contributor

@seemethere merged this pull request in ad4467b.

hwangdeyu pushed a commit to hwangdeyu/pytorch that referenced this pull request Jan 6, 2021
@seemethere
.github: Add action workflow to update S3 HTMLS (pytorch#49509)
cfd0951 
Summary:
Successful run: https://github.com/pytorch/pytorch/runs/1572315901

Signed-off-by: Eli Uriegas <eliuriegas@fb.com>

Pull Request resolved: pytorch#49509

Reviewed By: walterddr

Differential Revision: D25619133

Pulled By: seemethere

fbshipit-source-id: 092ab12535f3bf4fc85bbfc690d3f5b10a5f8791
@facebook-github-bot facebook-github-bot deleted the seemethere/add_s3_updater_action branch January 27, 2021 18:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@facebook-github-bot facebook-github-bot facebook-github-bot left review comments

+1 more reviewer

@walterddr walterddr walterddr approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

cla signed Merged

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@seemethere @facebook-github-bot @samestep @walterddr