All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rishikesh K Rajak <risrajak@linux.vnet.ibm.com>
To: Lucas Meneghel Rodrigues <lmr@redhat.com>
Cc: LTP list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] Remove libevent?
Date: Thu, 11 Mar 2010 20:54:30 +0530	[thread overview]
Message-ID: <20100311152430.GA3526@linux.vnet.ibm.com> (raw)
In-Reply-To: <1268312580.2518.12.camel@localhost.localdomain>

On Thu, Mar 11, 2010 at 10:03:00AM -0300, Lucas Meneghel Rodrigues wrote:
> On Wed, 2010-03-10 at 21:11 -0800, Garrett Cooper wrote:
> > Hi all,
> >     I just looked at the latest libevent, and I'm typically not one to
> > suggest this, but because libevent switched over to libtool in the 2.x
> > release (which is a pain in the ass to integrate), I think we just
> > drop the libevent testcase(s). I assume the maintainers run their
> > testcases on a subset of Unix machines, so it would just be an
> > annoying earmark that LTP has to maintain a dead // useless version of
> > libevent (eventually our version will go out of date and the code that
> > we have will bear little relevance and may be more buggy than the
> > latest version which should have appropriate tests and be executed and
> > triaged appropriately upstream).
> 
> +1. Of course I am not in a position of saying something about what it
> should be done, but I totally agree that LTP should strive in keeping
> only well maintainted tests. It's harmful to keep unmantained code, it
> bitrots and tends to make everyone's life difficult.

Well said Lucas & garret. We need to really look for some outdated testcase
currently existing with LTP. I can look into it incrementally, but like garret
if someone come to know about outdated testcase with LTP or some tetssuit which
need renewal, please let us know. We will work to renew them on high priority.

Some of the testsuits i am looking are:
    - cpu hot plug
    - memory hotplug

-Rishi


------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2010-03-11 15:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11  5:11 [LTP] Remove libevent? Garrett Cooper
2010-03-11 13:03 ` Lucas Meneghel Rodrigues
2010-03-11 15:24   ` Rishikesh K Rajak [this message]
2010-03-12  6:13     ` Garrett Cooper

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=20100311152430.GA3526@linux.vnet.ibm.com \
    --to=risrajak@linux.vnet.ibm.com \
    --cc=lmr@redhat.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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.