netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Jonathan Day <imipak@yahoo.com>
Cc: netdev@oss.sgi.com
Subject: Re: Automated linux kernel testing results
Date: Mon, 06 Jun 2005 11:30:48 -0700	[thread overview]
Message-ID: <42A49658.7060608@us.ibm.com> (raw)
In-Reply-To: <20050604050123.9897.qmail@web31504.mail.mud.yahoo.com>

Jonathan Day wrote:

> What I have not (yet) seen is any work on relating the
> results. Is a bug in the design? The implementation?
> Some combination thereof? Is something correctly
> written but not functioning because something it
> depends on isn't working correctly?

Currently, you can get some idea (kernel didn't
build, machine couldn't reboot, or if the system
crashes during the tests, crash info etc.  Looking
into whether the cause is a design bug or an
implementation bug is likely beyond automation.

> It would even be useful if we could cross-reference
> some of the benchmarks with the Linux graphing
> project, so that we could see how the complexity of

I believe they do (ping Martin for details) have some
plans to graph stuff, and possibly info could be sucked
out of the data/results provided to feed other people's
needs.

> Test suites are necessary. Test suites are great.
> Anyone working on a test suite deserves many kudos and
> much praise. Test suites that are relatable enough
> that you can see the same problem from different
> angles -- those are worth their printout weight in
> gold.

Yeah. :).

thanks,
Nivedita

      reply	other threads:[~2005-06-06 18:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-04  0:20 Automated linux kernel testing results Nivedita Singhvi
2005-06-04  5:01 ` Jonathan Day
2005-06-06 18:30   ` Nivedita Singhvi [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=42A49658.7060608@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=imipak@yahoo.com \
    --cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).