From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/3] doc: Clarify that the only public CI testing is build only
Date: Thu, 9 May 2024 12:04:42 +0200 [thread overview]
Message-ID: <Zjyfukg9pEwAb4aP@yuki> (raw)
In-Reply-To: <20240419124221.207445-2-pvorel@suse.cz>
Hi!
> Also convert .github/workflows/ci.yml as link to github
> (unfortunately that remove code formatting).
>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> doc/developers/writing_tests.rst | 4 ++--
> doc/users/supported_systems.rst | 9 +++++++++
> 2 files changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/doc/developers/writing_tests.rst b/doc/developers/writing_tests.rst
> index 032fbcbd5..3db56a558 100644
> --- a/doc/developers/writing_tests.rst
> +++ 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>`_
^
build
> 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
^
build
> +`.github/workflows/ci.yml <https://github.com/linux-test-project/ltp/blob/master/.github/workflows/ci.yml>`_.
>
> .. 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.
Maybe a bit better "There is no CI for the actual test runs."
> 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, pleae check
^
build
> +`.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
> --
> 2.43.0
>
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-05-09 10:05 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
2024-05-09 10:04 ` Cyril Hrubis [this message]
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=Zjyfukg9pEwAb4aP@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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.