[JBoss JIRA] (JBTM-2115) Not all classes are under code coverage
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2115?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-2115:
-----------------------------------
Fix Version/s: 5.next
(was: 5.2.3.Final)
> Not all classes are under code coverage
> ---------------------------------------
>
> Key: JBTM-2115
> URL: https://issues.jboss.org/browse/JBTM-2115
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Affects Versions: 5.0.1
> Reporter: Michael Musgrove
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.next
>
>
> The following poms contain skipped classes for code coverage:
> ArjunaCore/arjuna/pom.xml
> ArjunaJTA/jdbc/pom.xml
> ArjunaJTA/jta/pom.xml
> ArjunaJTA/spi/pom.xml
> XTS/localjunit/pom.xml
> We should aim to test everything
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1804:
-----------------------------------
Fix Version/s: 5.next
(was: 5.2.3.Final)
> JTS remote tests not run and no code coverage
> ---------------------------------------------
>
> Key: JBTM-1804
> URL: https://issues.jboss.org/browse/JBTM-1804
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: JTS, Testing
> Affects Versions: 5.0.0.M3
> Reporter: Mark Little
> Assignee: Amos Feng
> Fix For: 5.next
>
>
> The tests in .remote. package for JTS are not run by default. We should consider adding a build option so that they are run (will require some mods to the tests since many of them are client/server based - see associated Readme.txt files); don't run them by default since they will add delay to a normal build.
> It would then be beneficial to have them instrumented by emma to get code coverage.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (JBTM-2234) out of memory when logging more messages than heap size (surefire issue)
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2234?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-2234:
-----------------------------------
Fix Version/s: 5.next
(was: 5.2.3.Final)
> out of memory when logging more messages than heap size (surefire issue)
> ------------------------------------------------------------------------
>
> Key: JBTM-2234
> URL: https://issues.jboss.org/browse/JBTM-2234
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Performance Testing
> Affects Versions: 5.0.2
> Environment: JTS testing
> Reporter: Michael Musgrove
> Assignee: Amos Feng
> Priority: Optional
> Fix For: 5.next
>
>
> Running com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 on JacORB with about 500000 transactions results in an OOM error because surefire keeps in logs in memory until the test has finished.
> In this particular test jacorb logs messages at INFO level for each transaction resulting in excessive memory requirements. We can't make the heap too large because the default JVM is 32 bit. However, we could fix it by reducing the jacorb log level to WARN.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (JBTM-2409) XARecoveryModuleHelpersUnitTest hang
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2409?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-2409:
-----------------------------------
Fix Version/s: 5.next
(was: 5.2.3.Final)
> XARecoveryModuleHelpersUnitTest hang
> ------------------------------------
>
> Key: JBTM-2409
> URL: https://issues.jboss.org/browse/JBTM-2409
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Recovery
> Affects Versions: 5.1.1
> Reporter: Michael Musgrove
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
> Attachments: 32287.jstack
>
>
> The test checks that recovery helpers can be removed at the correct stages during recovery scans. The CI job http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/196 shows the hang.
> The junit test thread:
> - starts 2 threads that will remove a recovery helper
> - triggers xaRecoveryModule.periodicWorkFirstPass()
> - triggers xaRecoveryModule.periodicWorkSecondPass()
> - joins with remover threads
> The jstack output shows:
> - the two threads in the process of removing a recovery helper and are waiting for the first pass to finish;
> - the junit test thread is waiting to join with these two threads;
> Since both recovery passes must have completed it looks like the remover threads weren't notified when the first pass completed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (JBTM-2433) TransactionRolledBackException in MultiCloseTest
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2433?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-2433:
-----------------------------------
Fix Version/s: 5.next
(was: 5.2.3.Final)
> TransactionRolledBackException in MultiCloseTest
> ------------------------------------------------
>
> Key: JBTM-2433
> URL: https://issues.jboss.org/browse/JBTM-2433
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: XTS
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Priority: Minor
> Fix For: 5.next
>
> Attachments: com.arjuna.wstx.tests.arq.ba.MultiCloseTest-output.txt
>
>
> It looks like this failure has been caused by the race condition in WS-BA. In our tests it should be handled by the Byteman rule, but seems that for an unknown reason it has still failed in this occasion.
> {code}
> -------------------------------------------------------------------------------
> Test set: com.arjuna.wstx.tests.arq.ba.MultiCloseTest
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.117 sec <<< FAILURE!
> testMultiClose(com.arjuna.wstx.tests.arq.ba.MultiCloseTest) Time elapsed: 2.5 sec <<< ERROR!
> com.arjuna.wst.TransactionRolledBackException: null
> at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95)
> at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157)
> at com.arjuna.wstx.tests.arq.ba.MultiCloseTest.testMultiClose(MultiCloseTest.java:71)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months