Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Reply-To: <nhv AT cape DOT com>
From: "Norman Vine" <nhv AT cape DOT com>
To: <cygwin-developers AT cygwin DOT com>
Subject: RE: cygwin slowdown in current cvs version -- need a volunteer
Date: Sat, 8 Sep 2001 13:32:42 -0400
Message-ID: <002a01c1388c$44785c00$a300a8c0@nhv>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26
In-Reply-To: <20010908130309.A12339@redhat.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Importance: Normal

Christopher Faylor writes:
>>
>Can someone volunteer to run regressions like this when I announce that
>1.3.3 is about to be released?  I did run the test suite this time but
>I would like someone else to be doing this.

>I'd like to see someone running cygwin regression tests on a regular
>basis.  Will anyone volunteer?
>
>This essentially entails running "make check" in the winsup/testsuite
>directory and will involve coming up with some kind of method of timing
>cygwin.  Maybe just a build of cygwin and/or newlib is adequate.

Chris

I already almost do this on a ~'weekly' basis 

I already record the time it takes to do a fresh
configure make install   
on the files garnered from
cvs co winsup

so I just need to add the additional make check
inside of another timer wrapper in my python script.

what kind of report do we want ??

Norman