You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/contribute/ci.rst
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -113,11 +113,11 @@ Dealing with Flakiness
113
113
^^^^^^^^^^^^^^^^^^^^^^
114
114
115
115
If you notice a failure on your PR that seems unrelated to your change, you should
116
-
search [recent GitHub issues related to flaky tests](https://github.com/apache/tvm/issues?q=is%3Aissue+%5BCI+Problem%5D+Flaky+>) and
117
-
[file a new issue](https://github.com/apache/tvm/issues/new?assignees=&labels=&template=ci-problem.md&title=%5BCI+Problem%5D+>)
116
+
search `recent GitHub issues related to flaky tests<https://github.com/apache/tvm/issues?q=is%3Aissue+%5BCI+Problem%5D+Flaky>`_ and
117
+
`file a new issue<https://github.com/apache/tvm/issues/new?assignees=&labels=&template=ci-problem.md&title=%5BCI+Problem%5D>`_
118
118
if you don't see any reports of the failure. If a certain test or class of tests affects
119
-
several PRs or commits on `main` with flaky failures, the test should be disabled via
120
-
[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
119
+
several PRs or commits on ``main`` with flaky failures, the test should be disabled via
120
+
`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
0 commit comments