-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Conversation
Hey @barry-jin , Thanks for submitting the PR
CI supported jobs: [windows-gpu, unix-gpu, miscellaneous, centos-gpu, unix-cpu, sanity, website, windows-cpu, clang, centos-cpu, edge] Note: |
@mxnet-bot run ci [centos-cpu, centos-gpu, miscellaneous, unix-cpu] |
Jenkins CI successfully triggered : [centos-gpu, unix-cpu, miscellaneous, centos-cpu] |
@mxnet-bot run ci [centos-gpu, unix-cpu] |
Jenkins CI successfully triggered : [centos-gpu, unix-cpu] |
@mxnet-bot run ci [centos-cpu, unix-gpu] |
Jenkins CI successfully triggered : [unix-gpu, centos-cpu] |
@@ -69,6 +69,9 @@ | |||
autosummary_generate = True | |||
numpydoc_show_class_members = False | |||
|
|||
# Disable SSL verification in link check. | |||
tls_verify = False |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does tls_verify is a GitLab Runner configuration? Shouldn't the tls_verify be disabled by default? Following the doc
tls_verify Enable or disable TLS verification of connections to Docker daemon. Disabled by default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, it's a configuration in sphinx to disable verifying the server certifications.
ref: https://www.sphinx-doc.org/en/master/usage/configuration.html#confval-tls_verify
@mxnet-bot run ci [unix-gpu] |
Jenkins CI successfully triggered : [unix-gpu] |
Description
Checklist
Essentials
Comments