From: Cyril Hrubis <chrubis@suse.cz>
To: Gustavo Padovan <gustavo.padovan@collabora.com>
Cc: David Gow <davidgow@google.com>,
Donald Zickus <dzickus@redhat.com>,
workflows <workflows@vger.kernel.org>,
automated-testing <automated-testing@lists.yoctoproject.org>,
linux-kselftest <linux-kselftest@vger.kernel.org>,
kernelci <kernelci@lists.linux.dev>,
Nikolai Kondrashov <nkondras@redhat.com>,
kernelci-members <kernelci-members@groups.io>,
"laura.nao" <laura.nao@collabora.com>
Subject: Re: [Automated-testing] [RFC] Test catalog template
Date: Fri, 18 Oct 2024 16:35:21 +0200 [thread overview]
Message-ID: <ZxJyKZD9vcKnwG0n@yuki.lan> (raw)
In-Reply-To: <192a002ee68.e1e6c6282027214.1199547115557464780@collabora.com>
Hi!
> Then there are other perspectives that crosses this. For example, many of the LTP and
> kselftests will just fail, but there is no accumulated knowledge on what the result of
> each test means. So understanding what is expected to pass/fail for each platform is
> a sort of dependance in this extensive documentation effort we are set ourselves for.
We are spending quite a lot of time to make sure LTP tests do not fail
unless there is a reason to. If you see LTP tests failing and you think
that they shouldn't just report it on the LTP mailing list and we will
fix that.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2024-10-18 14:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 20:32 Donald Zickus
2024-10-15 16:01 ` [Automated-testing] " Bird, Tim
2024-10-16 13:10 ` Cyril Hrubis
2024-10-16 18:02 ` Donald Zickus
2024-10-17 11:01 ` Cyril Hrubis
2024-10-16 18:00 ` Donald Zickus
2024-10-17 12:31 ` Minas Hambardzumyan
2024-10-18 19:44 ` Donald Zickus
2024-10-18 7:21 ` David Gow
2024-10-18 14:23 ` Gustavo Padovan
2024-10-18 14:35 ` Cyril Hrubis [this message]
2024-10-18 19:17 ` Mark Brown
2024-10-18 20:17 ` Donald Zickus
2024-10-19 6:36 ` David Gow
2024-11-06 17:01 ` Donald Zickus
2024-11-20 8:16 ` David Gow
2024-11-21 15:28 ` Donald Zickus
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=ZxJyKZD9vcKnwG0n@yuki.lan \
--to=chrubis@suse.cz \
--cc=automated-testing@lists.yoctoproject.org \
--cc=davidgow@google.com \
--cc=dzickus@redhat.com \
--cc=gustavo.padovan@collabora.com \
--cc=kernelci-members@groups.io \
--cc=kernelci@lists.linux.dev \
--cc=laura.nao@collabora.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=nkondras@redhat.com \
--cc=workflows@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox