All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] [RFC] doc: Add testers guide
Date: Mon, 9 Jun 2025 08:32:00 +0200	[thread overview]
Message-ID: <20250609063200.GA1402165@pevik> (raw)
In-Reply-To: <20250606132100.20145-1-chrubis@suse.cz>

Hi Cyril,

very nice reading, thank you!

I found one more typo to these which Ricardo and Alok Tiwari found:

+and skill one cay say as much as is needed write the kernel code.
cay -> can

With these typo fixed:
Reviewed-by: Petr Vorel <pvorel@suse.cz>

> +It's a good idea to start small with an evironment that models your production.
> +Once that works well you can try different configurations. Select a few
> +interesting ones and run them for some time in order to get an idea of their
> +usefulness. If you are feeling adventurous you may try to measure and compare
> +actual test coverage with one of the tools such as lcov. If you do so do not

People can use search engines, but maybe having lcov, pareto principle and kirk as links?

`lcov <https://github.com/linux-test-project/lcov>`_.

Maybe point out in "Debugging test failures" section about `-iN` or `-IN`
possibility and that how single core vs. more cores can influence the result?

Kind regards,
Petr

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

  parent reply	other threads:[~2025-06-09  6:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-06 13:21 [LTP] [PATCH] [RFC] doc: Add testers guide Cyril Hrubis
2025-06-06 14:13 ` Andrea Cervesato via ltp
2025-06-06 15:03 ` Ricardo B. Marlière via ltp
2025-06-08 16:21 ` [LTP] [External] : " ALOK TIWARI via ltp
2025-06-09  6:32 ` Petr Vorel [this message]
2025-06-09 14:52 ` [LTP] " Wei Gao via ltp

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=20250609063200.GA1402165@pevik \
    --to=pvorel@suse.cz \
    --cc=chrubis@suse.cz \
    --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.