Here's the parts of the build log that show which test cases fail with
gcj-4.3[junit] Testsuite: org.apache.lucene.document.TestDateTools
[junit] Tests run: 5, Failures: 1, Errors: 0, Time elapsed: 5.689 sec
[junit]
[junit] Testcase:
testStringtoTime(org.apache.lucene.document.Tes
Package: gcj-4.3
Version: 4.3-20080202-1
Severity: normal
The Lucene package contains a large number of unit tests. All tests succeed when
building using Sun JDK 5. When building using gcj-4.3 (with gcj-java-compat-dev
from unstable), quite a few unit tests fail. Upon a suggestion by Michael Koch
Hi,
Sorry for the delay.
When I compile with gcj 4.1 and then run with gij-4.1, I get the error. If
I run the same class file with gij-4.2, everything's OK.
It looks like the issue is (or was) in the classpath libs, in
java/util/Calendar.java. The gcj4.2-src source package has some extra
stateme
On Wed, July 18, 2007 14:04, Matthias Klose wrote:
> Jan-Pascal van Best writes:
>> Hi,
>>
>> I forgot to mention that this bug triggers a unit test failure in Lucene
>> 2.2.0 (Debian package liblucene2-java), meaning the the Lucene package
>> cannot be built
Hi,
I forgot to mention that this bug triggers a unit test failure in Lucene
2.2.0 (Debian package liblucene2-java), meaning the the Lucene package
cannot be built using gcj, and so cannot go into Debian main (it is build
using the Sun toolchain now).
Jan-Pascal
Package: gcj-4.1
Version: 4.1.1-20
Severity: normal
When running the following code from a CEST locale:
Calendar cal = Calendar.getInstance();
System.out.println( "Calendar: " + cal.toString() );
cal.setTimeZone(TimeZone.getTimeZone("GMT"));
cal.set(1970, 0, 1,// year=1970, mo
6 matches
Mail list logo
