Testsuite's log4j was configured to print DEBUG messages to system.out.
This leads to a large TESTS-TestSuites.xml file.
There are two targets in build.xml:
tests-report-xml
tests-report-text
The first one generates testsuite/output/reports/text/TESTS-TestSuites.txt
The second one testsuite/output/reports/xml/TESTS-TestSuites.xml
Both files are small summaries (see below).
Both targets uses a XSL Transformation to transform this huge TESTS-TestSuites.xml file.
If this file is larger than 100MB, JAVA's embedded XSLT is unable finish this
process:
812 tests = 98 MB = 11 minutes 27 seconds
813 tests = 100 MB = 21 minutes 26 seconds
817 tests (the whole testsuite) = 111MB = OOME after over 80 minutes
So we can:
- use another XSLT - STX, but this needs new stylesheets, new libraries
- make the noisiest tests less verbose by commenting log.debug()
- make log4j less verbose (this was already done by changing level from DEBUG to FATAL)
- skip both targets above - do we need these files generated by that targets?
TESTS-TestSuites.txt:
**********************
<?xml version="1.0" encoding="UTF-8"?>
<time-of-test>2007-01-25.10-47</time-of-test><jdk-vendor>Sun
Microsystems
Inc.</jdk-vendor><jdk-version>1.4.2_09</jdk-version><jvm-vm-spec-version>1.0</jvm-vm-spec-version><jvm-name>Java
HotSpot(TM) Client
VM</jvm-name><jvm-version>1.4.2_09-b05</jvm-version><jvm-info>mixed
mode</jvm-info><java-spec-version>1.4</java-spec-version><java-class-version>48.0</java-class-version><os-name>Linux</os-name><os-arch>i386</os-arch><os-version>2.6.9-42.0.2.ELsmp</os-version>4167416511
**********************
TESTS-TestSuites.txt:
**********************
JBoss daily test results
SUMMARY
Number of tests run: 4167
--------------------------------------------
Successful tests: 4165
Errors: 1
Failures: 1
--------------------------------------------
[time of test: 2007-01-25.10-47 GMT]
[java.version: 1.4.2_09]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2_09-b05]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.6.9-42.0.2.ELsmp]
Useful resources:
-
http://jboss.sourceforge.net/junit-results/32/2007-01-25.10-47 for
the junit report of this test.
NOTE: If there are any errors shown above - this mail is only highlighting
them - it is NOT indicating that they are being looked at by anyone.
It is assumed that whoever makes change(s) to jboss that
break the test will be fixing the test or jboss, as appropriate!
--------------------------------------------
DETAILS OF ERRORS
Suite: org.jboss.test.pooled.test.SSLSocketsUnitTestCase
Test: testClientCertSSLAccess
Type: error
Exception: java.rmi.AccessException
Message: SecurityException; nested exception is:
javax.security.auth.login.FailedLoginException: Supplied Credential did not match existing
credential for null
---------------------------------
Suite: org.jboss.test.security.test.SRPLoginModuleUnitTestCase
Test: testSRPLoginWithAuxChallenge
Type: failure
Exception: junit.framework.AssertionFailedError
Message: Unable to complete login: Failed to complete SRP login, msg=Failed to encrypt
aux challenge
---------------------------------
**********************
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006616#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...