You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tvm.apache.org by tl...@apache.org on 2026/02/17 18:50:33 UTC
(tvm) branch main updated: [DOC] Fix various RST issues (#18789)
This is an automated email from the ASF dual-hosted git repository.
tlopex pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tvm.git
The following commit(s) were added to refs/heads/main by this push:
new bcd716bb8c [DOC] Fix various RST issues (#18789)
bcd716bb8c is described below
commit bcd716bb8c5507f2e6a8de05c1cbb86e530a824a
Author: Ruslan Baratov <x...@ruslo.dev>
AuthorDate: Wed Feb 18 02:50:27 2026 +0800
[DOC] Fix various RST issues (#18789)
Fix various RST issues in files:
- docs/contribute/ci.rst
- docs/contribute/code_guide.rst
---
docs/contribute/ci.rst | 8 ++++----
docs/contribute/code_guide.rst | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/docs/contribute/ci.rst b/docs/contribute/ci.rst
index a175ed10b3..ef64856ab0 100644
--- a/docs/contribute/ci.rst
+++ b/docs/contribute/ci.rst
@@ -113,11 +113,11 @@ Dealing with Flakiness
^^^^^^^^^^^^^^^^^^^^^^
If you notice a failure on your PR that seems unrelated to your change, you should
-search [recent GitHub issues related to flaky tests](https://github.com/apache/tvm/issues?q=is%3Aissue+%5BCI+Problem%5D+Flaky+>) and
-[file a new issue](https://github.com/apache/tvm/issues/new?assignees=&labels=&template=ci-problem.md&title=%5BCI+Problem%5D+>)
+search `recent GitHub issues related to flaky tests <https://github.com/apache/tvm/issues?q=is%3Aissue+%5BCI+Problem%5D+Flaky>`_ and
+`file a new issue <https://github.com/apache/tvm/issues/new?assignees=&labels=&template=ci-problem.md&title=%5BCI+Problem%5D>`_
if you don't see any reports of the failure. If a certain test or class of tests affects
-several PRs or commits on `main` with flaky failures, the test should be disabled via
-[pytest's @xfail decorator](https://docs.pytest.org/en/6.2.x/skipping.html#xfail-mark-test-functions-as-expected-to-fail) with [`strict=False`](https://docs.pytest.org/en/6.2.x/skipping.html#strict-parameter) and the relevant issue linked in the
+several PRs or commits on ``main`` with flaky failures, the test should be disabled via
+`pytest's @xfail decorator <https://docs.pytest.org/en/6.2.x/skipping.html#xfail-mark-test-functions-as-expected-to-fail>`_ with `strict=False <https://docs.pytest.org/en/6.2.x/skipping.html#strict-parameter>`_ and the relevant issue linked in the
disabling PR.
.. code-block:: python
diff --git a/docs/contribute/code_guide.rst b/docs/contribute/code_guide.rst
index 6648660ce2..ad09610ac9 100644
--- a/docs/contribute/code_guide.rst
+++ b/docs/contribute/code_guide.rst
@@ -98,7 +98,7 @@ Python Code Styles
The pylint check ``no-else-return`` is disabled to allow for this
distinction. See further discussion `here
- <https://github.com/apache/tvm/pull/11327>`.
+ <https://github.com/apache/tvm/pull/11327>`_.
.. code:: python