[XALANJ-2624] Xalan-J test results

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.7.2
• Security Level: No security risk; visible to anyone (Ordinary problems in Xalan projects. Anybody can view the issue.)
• Assignee: Steven J. Hathaway
• Reporter: Mukul Gandhi
• Created: 06/May/19 06:18
• Updated: 14/Jun/23 18:21

Description

I'm sharing test results that i've produced (provided in the archive files that are attached with this jira issue), by running tests available on Xalan-J gitbox repos (the tests and product codebase available as of today).

The attached test results are for following Xalan-J gitbox locations,

https://gitbox.apache.org/repos/asf/xalan-java.git (branch xalan-j_2_7_1_maint)

https://gitbox.apache.org/repos/asf/xalan-test.git (master)

I've run following two Xalan-J test Ant targets to produce the attached test reports,

smoketest : all of these tests pass

alltest : Lot many of these pass. Number of these fail as well. I feel that, the reports of "alltest" needs to be investigated for any needed actions. I had also provided the line, set JAVA_OPTS='-Xms1024m -Xmx3072m' in build.bat (for windows platform) before running 'alltest' target (it seems that, the Ant target 'alltest' requires a higher memory by the JVM).

To start with I think, the files ResultReportMini.html & ResultReport.html (provided in the attached archives, that I've produced) can be looked at to investigate the test results.

I hope that, someone would look at the attached reports, and suggest the next course of actions for meeting a healthy Xalan-J test results status.

Issue Links

• is related to: XALANJ-2634 Improve build: add CI, run xalan-test in CI, download jars from Central