From: Steven Rostedt <rostedt@goodmis.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: ksummit-discuss@lists.linuxfoundation.org,
Carlos O'Donell <carlos@redhat.com>,
Shuah Khan <shuahkh@osg.samsung.com>,
Thorsten Leemhuis <linux@leemhuis.info>,
linux-api@vger.kernel.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
Date: Wed, 5 Jul 2017 11:27:07 -0400 [thread overview]
Message-ID: <20170705112707.54d7f345@gandalf.local.home> (raw)
In-Reply-To: <a462fb3b-a6d4-e969-b301-b404981de224@roeck-us.net>
On Wed, 5 Jul 2017 08:16:33 -0700
Guenter Roeck <linux@roeck-us.net> wrote:
> The reproducers for several of the usb fixes I submitted recently took hours of
> stress test to reproduce the underlying problems. I have one more to fix which
> takes days to reproduce, if at all (I have seen that problem only two or three
> times during weeks of stress test). Due to the nature of the problems, reproducing
> them heavily depended on the underlying hardware. None of the reproducers can
> guarantee that the problem is fixed; they are intended to show the problem,
> not that it is fixed. This happens a lot with race conditions - in many cases
> it is impossible to prove that the problem is fixed; one can only prove that
> it still exists.
>
> Echoing what you said, I have no idea how it would even be possible to write
> unit tests to verify if the problems I fixed are really fixed.
>
> Several of the fixes I have submitted are based on single-instance error logs with
> no reproducer. Many others are compile time fixes or fix problems found with code
> inspection (manual or automatic).
>
> If we start shaming people for not providing unit tests, all we'll accomplish is
> that people will stop providing bug fixes.
I need to be clearer on this. What I meant was, if there's a bug
where someone has a test that easily reproduces the bug, then if
there's not a test added to selftests for said bug, then we should
shame those into doing so.
A bug that is found by inspection or hard to reproduce test cases are
not applicable, as they don't have tests that can show a regression.
And I'm betting that those bugs are NOT REGRESSIONS! Most likely are
bugs that always existed, but because of the unpredictable hitting of
the bug (as you said, it required hours of stress tests to reproduce),
the bug was not previously hit during development. That's not a
regression, that's a feature.
Are we tracking regressions or just simply bugs?
-- Steve
next prev parent reply other threads:[~2017-07-05 15:27 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-02 17:51 Thorsten Leemhuis
2017-07-03 16:30 ` Steven Rostedt
2017-07-03 18:50 ` Dan Williams
2017-07-04 19:03 ` Thorsten Leemhuis
2017-07-05 12:45 ` Steven Rostedt
2017-07-05 13:09 ` Carlos O'Donell
2017-07-05 13:27 ` Steven Rostedt
2017-07-05 14:06 ` Greg KH
2017-07-05 14:28 ` Carlos O'Donell
2017-07-05 14:33 ` Steven Rostedt
2017-07-05 14:52 ` Mark Brown
2017-07-05 15:08 ` Carlos O'Donell
2017-07-05 16:10 ` Steven Rostedt
2017-07-06 11:34 ` Laurent Pinchart
2017-07-09 13:46 ` Thorsten Leemhuis
2017-07-05 14:33 ` Mark Brown
2017-07-05 14:36 ` Steven Rostedt
2017-07-05 14:50 ` James Bottomley
2017-07-05 14:56 ` Steven Rostedt
2017-07-05 15:09 ` James Bottomley
2017-07-05 15:20 ` Mark Brown
2017-07-05 15:40 ` Geert Uytterhoeven
2017-07-05 15:20 ` Steven Rostedt
2017-07-05 15:32 ` James Bottomley
2017-07-05 15:43 ` Steven Rostedt
2017-07-05 18:24 ` Daniel Vetter
2017-07-05 18:17 ` Daniel Vetter
2017-07-05 15:16 ` Guenter Roeck
2017-07-05 15:27 ` Steven Rostedt [this message]
2017-07-05 15:36 ` James Bottomley
2017-07-05 16:04 ` Steven Rostedt
2017-07-05 16:58 ` James Bottomley
2017-07-05 17:07 ` Steven Rostedt
2017-07-05 16:48 ` Guenter Roeck
2017-07-05 16:58 ` Dan Williams
2017-07-05 17:02 ` Steven Rostedt
2017-07-06 9:28 ` Mark Brown
2017-07-06 9:41 ` Daniel Vetter
2017-07-06 14:53 ` Theodore Ts'o
2017-07-06 21:28 ` Daniel Vetter
2017-07-06 14:48 ` James Bottomley
2017-07-07 10:03 ` Mark Brown
2017-07-31 16:54 ` Eric W. Biederman
2017-07-31 20:11 ` Steven Rostedt
2017-07-31 20:12 ` Eric W. Biederman
2017-08-02 16:53 ` Shuah Khan
2017-08-02 17:33 ` Eric W. Biederman
2017-08-02 17:46 ` Shuah Khan
2017-08-02 17:58 ` Shuah Khan
2017-08-02 18:04 ` Eric W. Biederman
2017-08-02 18:23 ` Randy Dunlap
2017-08-02 18:42 ` Shuah Khan
2017-08-03 3:03 ` Theodore Ts'o
2017-08-03 17:42 ` Bird, Timothy
2017-08-03 22:11 ` Shuah Khan
2017-08-03 18:51 ` Shuah Khan
2017-08-04 1:15 ` Theodore Ts'o
2017-07-07 3:33 ` Fengguang Wu
2017-07-07 4:52 ` Frank Rowand
2017-07-05 15:32 ` Greg KH
2017-07-05 15:36 ` Carlos O'Donell
2017-07-05 15:52 ` Steven Rostedt
2017-07-05 18:42 ` Greg KH
2017-07-05 18:29 ` Daniel Vetter
2017-07-06 22:24 ` Shuah Khan
2017-07-06 22:32 ` Steven Rostedt
2017-07-06 22:40 ` Shuah Khan
2017-07-05 16:54 ` Dan Williams
2017-07-05 18:45 ` Greg KH
2017-07-05 19:47 ` Dan Williams
2017-07-05 14:06 ` Carlos O'Donell
2017-07-05 15:47 ` Mark Brown
2017-07-07 6:15 ` Andrei Vagin
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=20170705112707.54d7f345@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=carlos@redhat.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=linux@roeck-us.net \
--cc=shuahkh@osg.samsung.com \
/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