All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] Automating kernel regression detection
Date: Wed, 26 Apr 2006 16:26:06 +0000	[thread overview]
Message-ID: <20060426162606.GB3570@stusta.de> (raw)
In-Reply-To: <OF731507F4.A2EFB236-ON8725715C.00518671-8625715C.0051FDE7@us.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]

On Wed, Apr 26, 2006 at 09:57:36AM -0500, James Kenefick wrote:

> Hi 

Hi James,

>    I was hoping I could get some members of this community to take
> a look at a project which identifies which kernel patch, in a set of 
> patches
> introduces a regression into the source tree, and provide feedback to
> the team developing the tool.
> 
> The tool is called PyReT and can be found at http://pyret.sf.net
> 
> Feedback can be provided directly to the project team via their
> mailing list.

my first impression is your project is a big design document with a big 
architecture searching for use cases...

There are already people doing regular LTP runs, there are people doing 
regular compile tests, and much more.

The big problem with kernel bugs is the manual work for debugging them, 
not the few steps required with the existing tools to bisect patches or 
git trees.

> thanks for your time
>   -James

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


[-- Attachment #2: Type: text/plain, Size: 168 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

      parent reply	other threads:[~2006-04-26 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-26 14:57 [KJ] Automating kernel regression detection James Kenefick
2006-04-26 16:12 ` Greg KH
2006-04-26 16:26 ` Adrian Bunk [this message]

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=20060426162606.GB3570@stusta.de \
    --to=bunk@stusta.de \
    --cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.