From: Thorsten Leemhuis <linux@leemhuis.info>
To: "ksummit@lists.linux.dev" <ksummit@lists.linux.dev>
Subject: [TECH TOPIC] regressions: our workflows are the biggest enemy
Date: Wed, 12 Jun 2024 08:34:42 +0200 [thread overview]
Message-ID: <5182e50a-3d13-4edc-8f2a-a024e0588177@leemhuis.info> (raw)
Hi! I just submitted the following as a talk/discussion for the kernel
summit track at LPC. Ciao, Thorsten
---
Outline the major pain points why Linux kernel regressions happen and
why resolving some takes a long time as observed by Thorsten during
three years of working as the kernel's regression tracker.
The talk among others will describe why some workflow patterns are what
frequently leads to regressions -- and why they are also a factor why
some subsystems fix regression quickly, while others take weeks or
months to resolve.
While at it, describe what testers, bug reporters, developers, and
maintainers can do to prevent regressions and resolve them more quickly.
Furthermore also cover regzbot, the Regression Tracking Bot Thorsten
uses for his work: what it learned in the recent past, what's on its
roadmap, and where it works poorly or well in practise.
While doing all of the above, keep the audience involved and foster
discussion about the discussed points and anything related.
Assuming Thorsten is invited to the Linux maintainers summit happening
right before the LPC, he'll start this session by quickly recapping what
has been discussed and decided regarding bug/regression reporting,
tracking and handling there.
next reply other threads:[~2024-06-12 6:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 6:34 Thorsten Leemhuis [this message]
2024-06-12 15:26 ` Steven Rostedt
2024-06-12 15:50 ` Guenter Roeck
2024-06-12 16:07 ` Thorsten Leemhuis
2024-06-12 18:35 ` Liam R. Howlett
2024-06-13 10:32 ` Thorsten Leemhuis
2024-06-12 18:37 ` Leon Romanovsky
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=5182e50a-3d13-4edc-8f2a-a024e0588177@leemhuis.info \
--to=linux@leemhuis.info \
--cc=ksummit@lists.linux.dev \
/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