[JBoss JIRA] Created: (JBTM-576) update unit tests
by Jonathan Halliday (JIRA)
update unit tests
-----------------
Key: JBTM-576
URL: https://jira.jboss.org/jira/browse/JBTM-576
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Testing
Affects Versions: 4.7.0
Reporter: Jonathan Halliday
Assignee: Jonathan Halliday
Fix For: 4.8.0
There are many unit tests that have lain dormant for some time. Convert them from DTF/junit3 to junit4, wire them to the build and make them pass.
This will be done incrementally, one module at a time, following the dependency chain e.g. common, ArjunaCore/arjuna, ArjunaCore/txoj, ... JTA/, .../JTS/...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBTM-1233) Corrupt files apearing during concurrent Hudson runs
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1233:
-----------------------------------
Summary: Corrupt files apearing during concurrent Hudson runs
Key: JBTM-1233
URL: https://issues.jboss.org/browse/JBTM-1233
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Testing
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.17.0, 5.0.0.M2
The narayana.sh build script builds narayana and jbossas each time it's run. Artefacts are installed to a maven repo that is shared among all Hudson jobs. This can cause corrupt files if multiple jobs write to the same location in the repo at the same time. This is a common occurrence as the Hudson QE cluster has many jobs that execute the narayana.sh script and it is not uncommon for these jobs to run at the same time.
A simple solution would be to have the script use a maven repo that is local to the Hudson slave, rather than the shared one that is used at the moment. This maven repo would need to defer to the shared maven repo for unavailable artefacts. New artefacts would be installed to the local repo. This would ensure no shared access occurs as the Hudson slave will only be used by one job at a time.
This configuration would need to be option (and non-default) as it would not be desirable for developer or Newcastle-Hudson use.
--
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
12 years, 3 months