[
https://issues.jboss.org/browse/JBTM-1382?page=com.atlassian.jira.plugin....
]
Michael Musgrove commented on JBTM-1382:
----------------------------------------
The JIRA asks for output to be sent to qa/testoutput (not qa). For a qa run against both
orbs if you look in the testoutput directory you will find two zips (testoutput-jacorb.zip
and testoutput-idlj.zip) which contain the testoutput directory and the TEST*txt files
corresponding to each run. To see it working look at the latest narayana-dualstack job (I
did notice that btny-pulls-narayana CI job does not archive testoutput so I have updated
that job config).
I think I may have misunderstood your requirement. Did you mean move all the TEST*txt
files into testoutput but leave the zip files in the qa directory.
QA build does not archive test group summary files
--------------------------------------------------
Key: JBTM-1382
URL:
https://issues.jboss.org/browse/JBTM-1382
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Testing
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Priority: Minor
Fix For: 5.0.0.M2
Original Estimate: 4 hours
Remaining Estimate: 4 hours
The QA test suite consists of a number of test groups. The build produces a summary file
showing the status of each sub test within a group (these are called TEST-<test
group>.txt and stored in the qa directory). We currently archive the qa/testoutput
directory but it would be useful to also archive these summary text files. Note that we
cannot rely on Jenkins to do this for us since the jts remote test group is executed twice
(once for each orb) and the files from the first run are overwritten.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira