Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (herse.apache.org: local policy)
Date: Fri, 13 Apr 2007 14:41:36 +0200
From: Ole Solberg <Ole.Solberg@Sun.COM>
Subject: Re: tinderbox web page with "full" hiistory does not show suite
 failures correctly
In-reply-to: <461F0CEE.9040303@sbcglobal.net>
Sender: Ole.Solberg@Sun.COM
To: derby-dev@db.apache.org
Message-id: <461F7A80.8030808@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <461F0CEE.9040303@sbcglobal.net>
User-Agent: Thunderbird 1.5.0.9 (X11/20061221)

Mike Matrigali wrote:
> When you go to the full history page
> (http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/Limited/index_all.html)
> 
> 
> It only lists derbyall failures, making it sort of hard to track down
> suite failures, I had to click on 0 failure cases.  It is too bad
> but I don't think there have actually been any 0 failure runs in
> quite awhile.  I would like to see at least the tinderbox runs reporting
> 0 failures before we consider doing a release (even better if all the
> regression runs reported 0 failures - it is fine by me to remove known
> bug test runs if they are reported in JIRA with appropriate priority).
> 

I'll fix these reports to also include the ...suites.All failures.
Thanks for reminding me!

-- 
Ole Solberg, Database Technology Group,
Sun Microsystems, Trondheim, Norway