Java DB testing and reporting infrastructure.
Failure continuous trunk (rev 175)
There were 16 failures.
Thanks for the explanation Bryan.
-Original Message-
From: Bryan Pendleton [mailto:bpendleton.de...@gmail.com]
Sent: Tuesday, July 19, 2016 9:53 AM
To: derby-dev@db.apache.org
Subject: Re: [Java DB - testing] Failure continuous trunk (rev 175)
> So the message from "in
So the message from "ingemar.ab...@oracle.com" is not from one of the systems
that is open to the public?
As far as I know that is true at this time.
I was concerned about the 16 failures message in that email and wanted to take
a look.
Several of those corporate build systems have been
were clean so I was wondering what that email was
referring to.
-Original Message-
From: Bryan Pendleton [mailto:bpendleton.de...@gmail.com]
Sent: Tuesday, July 19, 2016 9:38 AM
To: derby-dev@db.apache.org
Subject: Re: [Java DB - testing] Failure continuous trunk (rev 175)
On 7/19/20
On 7/19/2016 5:57 AM, Bergquist, Brett wrote:
Where does one find this build job so that the failures can be looked at?
Hi Brett,
It's a little bit tricky.
You can find information about the Apache build and test system here:
http://db.apache.org/derby/derby_tests.html
If you
Where does one find this build job so that the failures can be looked at?
-Original Message-
From: ingemar.ab...@oracle.com [mailto:ingemar.ab...@oracle.com]
Sent: Tuesday, July 19, 2016 2:20 AM
To: derby-dev@db.apache.org
Subject: [Java DB - testing] Failure continuous trunk (rev 175
Java DB testing and reporting infrastructure.
Failure continuous trunk (rev 175)
There were 16 failures.
