From: Laura Nao <laura.nao@collabora.com>
To: kernelci@lists.linux.dev
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Testing Quality Call notes - 2024-08-08
Date: Fri, 9 Aug 2024 18:25:57 +0200 [thread overview]
Message-ID: <20240809162557.32300-1-laura.nao@collabora.com> (raw)
Hello,
KernelCI is hosting a bi-weekly call on Thursday to discuss improvements
to existing upstream tests, the development of new tests to increase
kernel testing coverage, and the enablement of these tests in KernelCI.
Below is a list of the tests the community has been working on and their
latest status updates, as discussed in the last meeting held on
2024-08-08:
*KTAP performance counters*
- Upcoming presentation @LPC2024 by Tim Bird on adding benchmark results
to KTAP: https://lpc.events/event/18/contributions/1791/
- Proposing new system to handle benchmark data, composed of 3 parts:
adding syntax to KTAP to support benchmark values, using a set of
external criteria for interpreting benchmark results, an automated tool
to determine and set the reference values used in these criteria.
- One related topic for discussion is where to store the reference files
and the test configuration, including all details that might impact the
results.
*Missing devices kselftest*
- Proposing new kselftest to report devices that go missing in the system:
https://lore.kernel.org/all/20240724-kselftest-dev-exist-v1-1-9bc21aa761b5@collabora.com/#r
- Received feedback on the usability of the test and main unknowns about
management of reference files in tests
*Boot time test*
- RFC:
https://lore.kernel.org/all/20240725110622.96301-1-laura.nao@collabora.com/T/#ma568382acdc81af65c30fe3823a7be3e49f98108
- Got feedback on the potential use of scripts from pm-graph. The
bootgraph.py script could be adapted for the test with some
modifications, such as adding support for machine-readable output and
different ftrace configurations.
*Suspend/resume in cpufreq kselftest*
- Sent v2 for patch adding RTC wakeup alarm in the cpufreq kselftest:
https://lore.kernel.org/lkml/20240715192634.19272-1-shreeya.patel@collabora.com/
- Looking into using the sleepgraph.py script from pm-graph to calculate
suspend/hibernation and resume time:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/power/pm-graph/sleepgraph.py?h=v6.11-rc1
- Would require additional configs to be enabled in an automated
environment
*TAP conformance in kselftests and other fixes*
- Some dead selftests were removed:
https://lore.kernel.org/all/20240725110817.659099-1-usama.anjum@collabora.com
and
https://lore.kernel.org/all/20240725121212.808206-1-usama.anjum@collabora.com
- Bitmap test module conversion to KUnit was not accepted:
https://lore.kernel.org/lkml/49108735-c776-4b6f-8264-62a827dd7b26@collabora.com/T/
- Fixing error when kvm suite is built for unsupported architecure:
https://lore.kernel.org/kvm/c2aaa06e-e86d-4af9-bce4-6067e53cdf39@collabora.com/T/
Please reply to this thread if you'd like to join the call or discuss any
of the topics further. We look forward to collaborating with the community
to improve upstream tests and expand coverage to more areas of interest
within the kernel.
Best regards,
Laura Nao
reply other threads:[~2024-08-09 16:25 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=20240809162557.32300-1-laura.nao@collabora.com \
--to=laura.nao@collabora.com \
--cc=kernelci@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).