All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/3] doc: Clarify that the only public CI testing is build only
Date: Fri, 19 Apr 2024 15:53:54 +0200	[thread overview]
Message-ID: <20240419135354.GA211868@pevik> (raw)
In-Reply-To: <0df81a8e-d450-4806-b425-82867ca8da3d@suse.com>

Hi Andrea,

> > +++ b/doc/developers/writing_tests.rst
> > @@ -346,8 +346,8 @@ Testing builds with GitHub Actions
> >   Master branch is tested in `GitHub Actions <https://github.com/linux-test-project/ltp/actions>`_
> >   to ensure LTP builds in various distributions, including old, current and
> >   bleeding edge. ``gcc`` and ``clang`` toolchains are also tested for various
> > -architectures using cross-compilation. For a full list of tested distros, please
> > -check ``.github/workflows/ci.yml``.
> > +architectures using cross-compilation. For a full list of tested distros, please check
> > +`.github/workflows/ci.yml <https://github.com/linux-test-project/ltp/blob/master/.github/workflows/ci.yml>`_.
> Maybe we can store github link into a variable and use it around the
> documentation.
> I'm not sure if it works, but eventually take a look at:
> https://groups.google.com/g/sphinx-users/c/OitnjX8SIA4/m/7_kUL0TaCwAJ

Thanks for a tip. Well, I don't think it's not working, but maybe I'm wrong.

I tested it with following diff inspired by docs [1], but the text in the link
is: "issue `123`" instead of 123 being formatted as code. Maybe there is some
parameter which can be tweaked or we need find another extension or write patch
for sphinx.ext.extlinks.

Looking at sphinx_version_ref [2] it also uses `, thus it will likely not work
either.

Anyway, it's not important we just loose some formatting. It's sort of "nice to
have".

Kind regards,
Petr

[1] https://www.sphinx-doc.org/en/master/usage/extensions/extlinks.html
[2] https://sphinx-version-ref.readthedocs.io/en/stable/


diff --git doc/conf.py doc/conf.py
index fb3e83cf2..771efbb34 100644
--- doc/conf.py
+++ doc/conf.py
@@ -22,9 +22,13 @@ release = '1.0'
 
 extensions = [
     'linuxdoc.rstKernelDoc',
-    'sphinxcontrib.spelling'
+    'sphinxcontrib.spelling',
+    'sphinx.ext.extlinks'
 ]
 
+extlinks = {'issue': ('https://github.com/sphinx-doc/sphinx/issues/%s',
+                      'issue `%s`')}
+
 exclude_patterns = ["html*", '_static*']
 
 spelling_lang = "en_US"
diff --git doc/developers/documentation.rst doc/developers/documentation.rst
index 825495c50..73b76dcde 100644
--- doc/developers/documentation.rst
+++ doc/developers/documentation.rst
@@ -3,6 +3,8 @@
 Documentation
 =============
 
+:issue:`123`
+
 This section explains how to use and develop the LTP documentation. The current
 documentation format is written using
 `reStructedText <https://www.sphinx-doc.org/en/master/usage/restructuredtext/index.html>`_


> >   .. note::
> > diff --git a/doc/users/supported_systems.rst b/doc/users/supported_systems.rst
> > index 82774c2ef..a9086f4d8 100644
> > --- a/doc/users/supported_systems.rst
> > +++ b/doc/users/supported_systems.rst
> > @@ -3,6 +3,12 @@
> >   Supported systems
> >   =================
> > +Build testing is done with `GitHub Actions <https://github.com/linux-test-project/ltp/actions>`_.
> > +
> > +.. note::
> > +
> > +      There is no CI testing of the actual tests run.
> > +
> >   Kernel version
> >   --------------
> > @@ -38,6 +44,9 @@ Oldest tested distributions
> >         - 10.2.1
> >         - 11.0.1
> > +For a full list of tested distros, please tested distros, please check
> > +`.github/workflows/ci.yml <https://github.com/linux-test-project/ltp/blob/master/.github/workflows/ci.yml>`_.
> > +
> >   Older distributions are not officially supported, which means that it
> >   may or may not work. It all depends on your luck. It should be possible
> >   to compile latest LTP even on slightly older distributions than we

> Andrea


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2024-04-19 13:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19 12:42 [LTP] [PATCH 1/3] doc: Bump minimal supported kernel to 4.4 Petr Vorel
2024-04-19 12:42 ` [LTP] [PATCH 2/3] doc: Clarify that the only public CI testing is build only Petr Vorel
2024-04-19 13:18   ` Andrea Cervesato via ltp
2024-04-19 13:53     ` Petr Vorel [this message]
2024-05-09 10:04   ` Cyril Hrubis
2024-05-09 10:23     ` Petr Vorel
2024-05-09 13:34     ` Petr Vorel
2024-04-19 12:42 ` [LTP] [PATCH 3/3] doc: Update building docs section Petr Vorel
2024-04-19 13:07   ` Andrea Cervesato via ltp
2024-04-20  1:57 ` [LTP] [PATCH 1/3] doc: Bump minimal supported kernel to 4.4 Li Wang
2024-05-09  9:55 ` Cyril Hrubis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240419135354.GA211868@pevik \
    --to=pvorel@suse.cz \
    --cc=andrea.cervesato@suse.com \
    --cc=ltp@lists.linux.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.