From: Paul Larson <plars@linuxtestproject.org>
To: Doug Ramier <v2cibdr@us.ibm.com>
Cc: ltp-list@lists.sourceforge.net, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [LTP] LTP version 20030306
Date: 20 Mar 2003 16:41:40 -0600 [thread overview]
Message-ID: <1048200101.26917.228.camel@plars> (raw)
In-Reply-To: <OFA4093E14.AB316F7E-ON86256CEF.00784F88-86256CEF.0079F340@rchland.ibm.com>
On Thu, 2003-03-20 at 16:12, Doug Ramier wrote:
> After overcoming problems with the compilation, we are getting between 50
> and 130 failures on 64 and 32 bit versions which with 20030206 we had on
> the order of a dozen.
Quick suggestion, instead of sending a flame out to everyone you can
think of, try sending some specific information about the problem you're
having the the appropriate mailing list (ltp-list). Details will help
us solve your problem, ranting will not.
> I have a few questions:
> 1) Is everyone getting a "large" number of false failures?
No, again, details please
> 2) Are the tests checked out before being released by SourceForge?
Yes
> 3) Are the tests only verified on Intel? How about PowerPC and iSeries?
We can verify on the hardware we have available to us. Obviously we
don't have everything ever made, or even a sample of every architecture
supported by Linux. Being an open source project we depend on others to
let us know when they are having problems on an architecture that we
don't have. Are you volunteering?
> 4) Is there a version released after the release that has the 205 patches
> installed?
I'm not sure what "205 patches" you're referring to. We make monthly
releases, and fixes are made to cvs in the interim. You can pull from
the cvs tree to get the latest.
prev parent reply other threads:[~2003-03-20 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 22:12 Doug Ramier
2003-03-20 22:37 ` [LTP] " Robert Williamson
2003-03-20 22:41 ` Paul Larson [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=1048200101.26917.228.camel@plars \
--to=plars@linuxtestproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=v2cibdr@us.ibm.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
all inboxes | Powered by JetHome®