From: Gustavo Padovan <gustavo.padovan@collabora.com>
To: stable@vger.kernel.org
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Shreeya Patel <shreeya.patel@collabora.com>,
"kernelci@lists.linux.dev" <kernelci@lists.linux.dev>,
Greg KH <gregkh@linuxfoundation.org>
Subject: stable/LTS test report from KernelCI (2023-12-08)
Date: Fri, 8 Dec 2023 12:29:35 -0300 [thread overview]
Message-ID: <738c6c87-527e-a1c2-671f-eed6a1dbaef3@collabora.com> (raw)
Hello,
As discussed with Greg at LPC, we are starting an iterative process to
deliver meaningful stable test reports from KernelCI. As Greg pointed
out, he doesn't look at the current reports sent automatically from
KernelCI. Those are not clean enough to help the stable release process,
so we discussed starting over again.
This reporting process is a learning exercise, growing over time. We are
starting small with data we can verify manually (at first) to make sure
we are not introducing noise or reporting flakes and false-positives.
The feedback loop will teach us how to filter the results and report
with incremental automation of the steps.
Today we are starting with build and boot tests (for the hardware
platforms in KernelCI with sustained availability over time). Then, at
every iteration we try to improve it, increasing the coverage and data
visualization. Feedback is really important. Eventually, we will also
have this report implemented in the upcoming KernelCI Web Dashboard.
This work is a contribution from Collabora(on behalf of its clients) to
improve the Kernel Integration as whole. Moving forward, Shreeya Patel,
from the Collabora team will be taking on the responsibilities of
delivering these reports.
Without further ado, here's our first report:
## stable-rc HEADs:
Date: 2023-12-08
6.1:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/log/?h=45deeed0dade29f16e1949365688ea591c20cf2c
5:15:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/log/?h=e5a5d1af708eced93db167ad55998166e9d893e1
5.10:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/log/?h=ce575ec88a51a60900cd0995928711df8258820a
5:4:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/log/?h=f47279cbca2ca9f2bbe1178634053024fd9faff3
* 6.6 stable-rc was not added in KernelCI yet, but we plan to add it
next week.
## Build failures:
No build failures seen for the stable-rc/queue commit heads for
6.1/5.15/5.10/5.4 \o/
## Boot failures:
No **new** boot failures seen for the stable-rc/queue commit heads for
6.1/5.15/5.10/5.4 \o/
(for the time being we are leaving existing failures behind)
## Considerations
All this data is available in the legacy KernelCI Web Dashboard -
https://linux.kernelci.org/ - but not easily filtered there. The data in
this report was checked manually. As we evolve this report, we want to
add traceability of the information, making it really easy for anyone to
dig deeper for more info, logs, etc.
The report covers the hardware platforms in KernelCI with sustained
availability over time - we will detail this further in future reports.
We opted to make the report really simple as you can see above. It is
just an initial spark. From here your feedback will drive the process.
So really really tell us what you want to see next. We want FEEDBACK!
Best,
- Gus
--
Gustavo Padovan
Kernel Lead
Collabora Ltd.
Platinum Building, St John's Innovation Park Cambridge CB4 0DS, UK
Registered in England & Wales, no. 5513718
next reply other threads:[~2023-12-08 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 15:29 Gustavo Padovan [this message]
2023-12-08 15:58 ` stable/LTS test report from KernelCI (2023-12-08) Greg KH
2023-12-11 10:14 ` Guillaume Tucker
2023-12-11 13:07 ` Greg KH
2023-12-13 13:30 ` Guillaume Tucker
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=738c6c87-527e-a1c2-671f-eed6a1dbaef3@collabora.com \
--to=gustavo.padovan@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernelci@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=shreeya.patel@collabora.com \
--cc=stable@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