Mukul Gandhi created XALANJ-2624:
------------------------------------
Summary: Xalan-J test results
Key: XALANJ-2624
URL: https://issues.apache.org/jira/browse/XALANJ-2624
Project: XalanJ2
Issue Type: Task
Security Level: No security risk; visible to anyone (Ordinary problems in
Xalan projects. Anybody can view the issue.)
Affects Versions: 2.7.2
Reporter: Mukul Gandhi
Assignee: Steven J. Hathaway
Attachments: results_alltest.zip, results_smoketest.zip
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?p=xalan-java.git;a=shortlog;h=refs/heads/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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
