We have had problems checking out from the repository.
Looks like the same has happened this evening, so I am afraid tomorrows
results will be the same.
We will try to fix this ASAP.
Henri
[EMAIL PROTECTED] wrote:
[Auto-generated mail]
*Daily* 572980S1/2007-09-05 18:00:12 CEST
Failed
Due to a major power outage in Trondheim, not all tests were finished on
all platforms.
Everything is expected to be fine again tomorrow.
Henri
[EMAIL PROTECTED] wrote:
[Auto-generated mail]
*Daily* 568177/2007-08-21 18:00:12 CEST
Failed TestsOK Skip Duration Suite
+1
Henri
Rick Hillegas wrote:
Please vote on whether we should make Øystein Grøvlen a committer. The
vote will close at 5:00 pm San Francisco time on Tuesday August 28.
Hi!
For approx. 24 hours, www.tresher.com has been unavailable. We have
notified the owner of this site. We got the following answer: we're
working an issue in the datacenter. I should have more information later
today.
Hopefully this will be fixed quite soon. Sorry for the inconvenience!
The last couple of days reports for suitesAll on Solaris x64 (sol) have
shown 'UNKNOWN'.
The JUnit test has crashed with: Exception in thread main
java.lang.OutOfMemoryError: PermGen space
Because of this there is no complete log from JUnit and the reporting
scripts are unable to parse them
Hi Myrna!
I understand your concern and would like to share my thoughts.
I think a combination of 1) and 3) would be best.
I would prefer a release now, but understand the concerns in the
community and thereby the need for a new RC. After the 26th I will also
start a vacation, so that would
Tomorrows report will show some fewer platforms, since these machines
now are used for release-testing of 10.3.1.1.
Testing on the 10.2-branch has also been paused.
Henri
[EMAIL PROTECTED] wrote:
[Auto-generated mail]
*Daily* 554378/2007-07-08 18:00:10 CEST
Failed TestsOK Skip
2 platforms had to be taken out of the daily test to be used for
10.3.1.0-testing: SLES and Vista
SolN+1 had to be rebooted.
Henri
[EMAIL PROTECTED] wrote:
[Auto-generated mail]
*Daily* 548386/2007-06-18 18:00:06 CEST
Failed TestsOK Skip Duration Suite
The daily test does a new checkout.
Unfortunately the same thing happened this evening. I am afraid problems
are not being solved during a weekend.
Thanks,
Henri
Jean T. Anderson wrote:
Henri van de Scheur - Sun Norway wrote:
Probably due to some network trouble, the daily build did
Probably due to some network trouble, the daily build did not succeed
and no tests are being run. Hopefully better tomorrow
ERR 2007-06-16 18:06:26 Giving up checkout of
https://svn.apache.org/repos/asf/db/derby/code/trunk
ERR 2007-06-16 18:06:26 Checking out derby/code failed 3 attempts
David Van Couvering wrote:
On 6/13/07, Daniel John Debrunner [EMAIL PROTECTED] wrote:
David Van Couvering wrote:
+1, I agree it's just too tight for 10.3.
I'd like your response to my proposal for the experimental directory;
right now I'm moving forward with it (for checkin to the trunk
For several days now, reporting of our testing has had some failures
resulting in erroneous reports. My apologies for the inconvenience.
I hope to fix this tomorrow when I am back from a short Easter-vacation.
Henri
[EMAIL PROTECTED] wrote:
[Auto-generated mail]
*Daily* 524622S5/2007-04-01
The report send here, was from the day before. Something went wrong in
our daily building resulting in no tests run.
Todays build-procedure seems to be fine, so tomorrow test-results will
be posted as usual.
Henri
[EMAIL PROTECTED] wrote:
[Auto-generated mail]
*Daily* 514731/2007-03-05
Quite some tests had to be stopped: these were 'hanging', maybe also due
to what Ole has seen: Derby-2344.
Henri
[EMAIL PROTECTED] wrote:
[Auto-generated mail]
*Daily* 508011/2007-02-15 18:00:11 CET
Failed TestsOK Skip Duration Suite
Due to some environmental problems in our infrastructure, tests were not
started yesterday. So sorry for the inconvenience!
Tests are now running again, and the usual report will be send out tomorrow.
Henri
[EMAIL PROTECTED] wrote:
[Auto-generated mail]
*Daily* 497499/2007-01-18 18:00:10 MET
After 10.2.2.0 was released, testing on the 10.2-branch wasn't
reactivated. As long as I have machines available, I can reactivate
this, but I am afraid I do not have much resources to monitor this
and/or follow up. But since you ask, I guess the need for this testing
is apparent and I will
Test results for the 10.2.2.0 RC will be published at
http://dbtg.thresher.com/derby/test/
Tests have been run with jvm1.4, jvm1.5 and jvm1.6 on 16 different OS
platforms.
A summary-report wil be published here:
http://dbtg.thresher.com/derby/test/10.2.2.0_RC/TestReport.html
I have also
+1
Very good results. See http://wiki.apache.org/db-derby/TenTwoPlatformTesting
Henri
Rick Hillegas wrote:
Please download and test-drive the 10.2.2.0 candidate, then vote on
whether to accept it as a Derby release. The candidate lives at:
http://people.apache.org/~rhillegas/10.2.2.0/
Daniel John Debrunner wrote:
Henri van de Scheur - Sun Norway wrote:
+1
Very good results. See
http://wiki.apache.org/db-derby/TenTwoPlatformTesting
Did you have to move derbyTesting.jar into the same folder as the
other Derby jars to run the tests?
I did not do so myself (we have
+1
Henri
Jean T. Anderson wrote:
I propose that we add Laura Stewart as a committer for Derby.
+1
Henri
Andrew McIntyre wrote:
I am proposing that we add Myrna Van Lunteren ([EMAIL PROTECTED])
as a committer for Derby.
Mike Matrigali wrote:
Please vote +1 if you approve of Mamta as a committer.
+1
Henri
Testing on the 10.2 branch is sometimes interrupted due to allocation of
the testmachines for other purposes, but as for now tests are being run
regularly.
Results can be found under http://dbtg.thresher.com/derby/test/#10.2Branch
Henri
So sorry, but due to a failure under our build, no tests were run.
Problem has been fixed, and tomorrow results will appear again.
Henri
[EMAIL PROTECTED] wrote:
[Auto-generated mail]
** 464950/2006-10-17 18:00:09 MEST
**
Failed TestsOK Skip Duration Platform
+1
Daniel John Debrunner wrote:
I propose a vote for Fernanda Pizzorno as a Derby committer.
Fernanda worked on the implementation of scrollable updateable result
sets and has also submitted patches to fix a number of issues.
Fernanda is also currently jumping into converting tests to JUnit.
Sorry, but we had a build-failure resulting in no tests run.
We already switched to build 101 of jdk 1.6 before EoD api was removed
from our JDBC drivers.
[EMAIL PROTECTED] wrote:
[Auto-generated mail]
** 453654/2006-10-06 18:00:08 MEST
**
Failed TestsOK Skip Duration Platform
Andrew McIntyre wrote:
On 9/27/06, Henri van de Scheur - Sun Norway
[EMAIL PROTECTED] wrote:
That seems more logical. I have had no problems before until today with
this automatically generated mail. So your proposal might be the right
solution, although we might give it one more try as Andrew
Maybe this was caused by the fact that I am probably registered in the
list with an alias and now used my full mail-address?
No problem for me to use the alias instead if that helps.
Thanks for helping out!
Henri
Andrew McIntyre wrote:
On 9/27/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Ole Solberg wrote:
Andrew McIntyre wrote:
On 9/27/06, Henri van de Scheur - Sun Norway
[EMAIL PROTECTED] wrote:
Maybe this was caused by the fact that I am probably registered in the
list with an alias and now used my full mail-address?
No problem for me to use the alias instead
Nightly tests on 10.2 branch were started again yesterday.
Regards,
Henri
Henri van de Scheur - Sun Norway wrote:
This night and probably 2 more days, there will be no results showing
up for this type of testing. The machines are now being used for
testing the beta-candidate 10.2.1.1
Hi Rick and Mike!
I am sorry, but I can not publish these results without Ole's help, so
I hope we can do this the first thing on Monday.
FYI: derbyall is being run on
Linux RHEL4.0/64
Solaris 10/x64
Solaris 10 sparc
Windows 2003ee
On all platforms tests are performed with jvm1.4, jvm1.5
We (John Embretsen Henri van de Scheur) published a Summary testreport
on the site where Ole uses to publish his results:
http://www.multinet.no/~solberg/public/Apache/10.2.0.4_Snapshot/Testsummary_10.2.0.4.html
A list of platforms tested on is published as
Kathey Marsden wrote:
Andrew McIntyre wrote:
On 6/29/06, Jean T. Anderson [EMAIL PROTECTED] wrote:
Is the long description for DERBY-1327 needed? That release notes entry
mentions that it's fixed in 10.1.3.1 and it's listed down in the Bugs
Fixed section.
I included it at an earlier
Andrew McIntyre wrote:
On 6/29/06, Jean T. Anderson [EMAIL PROTECTED] wrote:
Is the long description for DERBY-1327 needed? That release notes entry
mentions that it's fixed in 10.1.3.1 and it's listed down in the Bugs
Fixed section.
I included it at an earlier request of Kathey Marsden. It
+1
We have run a testcycle on 10.1.3.1 with tests as specified below on
platforms as specified below.
We did NOT discover any regressions.
We saw only one new failure, as compared to tests on previous versions:
filed as http://issues.apache.org/jira/browse/DERBY-1430
We do not regard this as
We have run a testcycle on 10.1.3.0 with tests as specified below on
platforms as specified below.
We did NOT discover any regressions and we did NOT see any new failures.
All tests were run with both Sun jvm 1.5.0 and Sun jvm 1.4.2
Tests/testsuites run:
demo
derbyall
derbylang
It appears that we have hit a bad state of the tests in the repository
at svn revision 409481:
The problem is with the test harness / derby_tests.policy.
Between r409471 and r409565 the test harness die suddenly at RunTest:2552.
See
37 matches
Mail list logo
