From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] LTP TODO list
Date: Fri, 11 May 2018 14:42:47 +0200 [thread overview]
Message-ID: <20180511124247.GD17721@rei> (raw)
Hi!
As you may remeber I've asked previously here where to start tracking
LTP TODO list, we decided on GitHub and hence I started to put the
information there.
So far I've started with a rough estimate of missing syscall coverage, I
do expect this list easily to grow at least twice once I have a time to
dig deeper into it, but it's a start at least.
I've added a tag "missing coverage" where you can see what we are not
testing at the moment:
https://github.com/linux-test-project/ltp/labels/missing%20coverage
These issues vary a lot in complexity, some of them could be done under
an hour, some are three months jobs, this is inevitable as sometimes one
syscall is a gateway for a very complex functionality.
I'll also dump a list of CVE reproducers and regression tests that are
candidates to be turned into LTP tests that I currently have. Which will
go under reproducer tag:
https://github.com/linux-test-project/ltp/labels/reproducer
I would also like to encourage everyone of you to add issues there and
also feel free to pick any of these, just comment it with someting as
"working on it".
--
Cyril Hrubis
chrubis@suse.cz
reply other threads:[~2018-05-11 12:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180511124247.GD17721@rei \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox