FYI: https://bugs.eclipse.org/bugs/show_bug.cgi?id=270762 is also
impacted by IBM VM, but also by Sun Java 6 VM.
It should be easy to output expected
ordering to a file, then all future run of the test will check if get the same
ordering.
From: eclipselink-dev-bounces@xxxxxxxxxxx
[mailto:eclipselink-dev-bounces@xxxxxxxxxxx] On
Behalf Of David McCann
Sent: Friday, May 22, 2009 11:23
AM
To: Dev
mailing list for Eclipse Persistence Services
Cc: ejgwin@xxxxxxxxx
Subject: Re: [eclipselink-dev]
BUILD STATUS:: trunk cb build has test failures!
Looks
like another case of different map ordering in the IBM VM. I've checked
in a fix to the test case that should resolve this.
--Dave
eric.gwin@xxxxxxxxxx wrote:
TEST-CORE-SRG
Tests run:677 Failures:0 Errors:0
TEST-JPA-SRG
Tests run:172 Failures:0 Errors:0
TEST-MOXY-SRG
Tests run:323 Failures:1 Errors:0
TEST-SDO-SRG
Tests run:120 Failures:0 Errors:0
TEST-DBWS-SRG
Tests run:3 Failures:0 Errors:0
TEST-DBWS-UTILS-SRG
Tests run:21 Failures:0 Errors:0
-----------------------------------
Full Build log can be found on the build machine at:
/shared/rt/eclipselink/logs/bsb-trunk_cb_090521-1700.log
or on the download server at:
http://www.eclipse.org/eclipselink/downloads/build-failures.php
-----------------------------------
SVN Changes since Last Build:
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
--

David McCann | Principal Software
Engineer | EclipseLink Product
ORACLE
Corporation Canada
45 O'Connor St. Suite 400
| Ottawa, ON
K1P 1A4
613.288.4636 | 613.238.2818 (fax)