January 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-731) refactor qa tests to reduce code duplication

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-731?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-731: ------------------------------- Assignee: Ondřej Chaloupka > refactor qa tests to reduce code duplication > -------------------------------------------- > > Key: JBTM-731 > URL: https://issues.jboss.org/browse/JBTM-731 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 4.10.0 > Reporter: Jonathan Halliday > Assignee: Ondřej Chaloupka > > The qa tests include a massive about of almost but not quite identical code. Refactor to reduce duplication. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-576) update unit tests

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-576?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-576: ------------------------------- Assignee: Ondřej Chaloupka > update unit tests > ----------------- > > Key: JBTM-576 > URL: https://issues.jboss.org/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: Ondřej Chaloupka > Priority: Minor > > 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, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1407) Have a build option that builds JTS only against JacORB or IDLJ, but not both.

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1407?page=com.atlassian.jira.plugin.... ] Gytis Trikleris logged work on JBTM-1407: ----------------------------------------- Author: Gytis Trikleris Created on: 21/Jan/13 6:01 AM Start Date: 18/Jan/13 12:00 PM Worklog Time Spent: 10 minutes Issue Time Tracking ------------------- Remaining Estimate: 1 day (was: 1 hour) Time Spent: 6 hours, 50 minutes (was: 6 hours, 40 minutes) Worklog Id: (was: 12428422) > Have a build option that builds JTS only against JacORB or IDLJ, but not both. > ------------------------------------------------------------------------------ > > Key: JBTM-1407 > URL: https://issues.jboss.org/browse/JBTM-1407 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTS > Affects Versions: 4.17.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.0.0.M2 > > Time Spent: 6 hours, 50 minutes > Remaining Estimate: 1 day > > This boils down to supporting two new profiles: > ./build.sh -P jts-jacorb > ./build.sh -P jts-idlj -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1031) == replaced with equals() in objects comparison where appropriate

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1031?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1031: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > == replaced with equals() in objects comparison where appropriate > ----------------------------------------------------------------- > > Key: JBTM-1031 > URL: https://issues.jboss.org/browse/JBTM-1031 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 4.17.4, 5.0.0.M2 > > Time Spent: 1 hour, 20 minutes > Remaining Estimate: 0 minutes > > A recent bug in XTS recovery was caused by the use of == to compare Strings. String#equals(...) should have been used. > We need to search the XTS codebase for other occurrences of this type of bug. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1382) QA build does not archive test group summary files

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1382?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1382: ------------------------------------- I happened to notice that this: http://172.17.131.2/view/Narayana+BlackTie/job/JBTM-1382/lastSuccessfulBu... didn't have the TEST* in the zip? > 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1344) org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests Timeout (900mins)

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1344?page=com.atlassian.jira.plugin.... ] Paul Robinson logged work on JBTM-1344: --------------------------------------- Author: Paul Robinson Created on: 21/Jan/13 4:04 AM Start Date: 21/Jan/13 4:03 AM Worklog Time Spent: 1 hour, 30 minutes Issue Time Tracking ------------------- Remaining Estimate: 1 day, 6 hours, 30 minutes (was: 2 days) Time Spent: 1 hour, 30 minutes Worklog Id: (was: 12428421) > org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests Timeout (900mins) > ------------------------------------------------------------------------------------ > > Key: JBTM-1344 > URL: https://issues.jboss.org/browse/JBTM-1344 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TxBridge > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 4.17.3, 5.0.0.M2 > > Original Estimate: 2 days > Time Spent: 1 hour, 30 minutes > Remaining Estimate: 1 day, 6 hours, 30 minutes > > See: http://172.17.131.2/job/jbossts-narayana-java6/81/ -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1344) org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests Timeout (900mins)

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1344?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1344: -------------------------------- Original Estimate: 2 days Remaining Estimate: 2 days > org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests Timeout (900mins) > ------------------------------------------------------------------------------------ > > Key: JBTM-1344 > URL: https://issues.jboss.org/browse/JBTM-1344 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TxBridge > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 4.17.3, 5.0.0.M2 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > See: http://172.17.131.2/job/jbossts-narayana-java6/81/ -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1344) org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests Timeout (900mins)

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1344?page=com.atlassian.jira.plugin.... ] Paul Robinson edited comment on JBTM-1344 at 1/21/13 3:41 AM: -------------------------------------------------------------- Notice that it's 'basic test' that is hanging. This test does not cause a crash, which makes it simpler to figure out what's going on. The thread dump doesn't seem to show any of the TXBridge tests or code in the stack traces, so it's not clear what the test is waiting for. It's possible that we could be missing some output from the console due to Hudson not flushing the log before it was killed. Assuming we are not, the next line of output you would expect (captured from a successful run) is: {code} installing: RULE org.jboss.byteman.contrib.dtest.Instrumentor_org.jboss.jbossts.txbridge.tests.outbound.utility.TestVolatileParticipant_error_remotetrace_entry {code} This line of output would be produced when the test calls: {code} instrumentedTestVolatileParticipant = instrumentor.instrumentClass(TestVolatileParticipant.class); {code} And in particular when the method 'error' is instrumented by 'org.jboss.byteman.contrib.dtest.Instrumentor#instrumentClass'. There is no refrence to 'dtest' in the stack dump. Also, the only Byteman thread in the stack dump is as follows: {code} "Thread-0" daemon prio=10 tid=0x54943000 nid=0x7686 runnable [0x548fe000] java.lang.Thread.State: RUNNABLE at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398) at java.net.ServerSocket.implAccept(ServerSocket.java:522) at java.net.ServerSocket.accept(ServerSocket.java:490) at org.jboss.byteman.agent.TransformListener.run(TransformListener.java:133) {code} was (Author: paul.robinson): Notice that it's 'basic test' that is hanging. This test does not cause a crash, which makes it simpler to figure out what's going on. The thread dump doesn't seem to show any of the TXBridge tests or code in the stack traces, so it's not clear what the test is waiting for. It's possible that we could be missing some output from the console due to Hudson not flushing the log before it was killed. Assuming we are not, the next line of output you would expect (captured from a successful run) is: {code} installing: RULE org.jboss.byteman.contrib.dtest.Instrumentor_org.jboss.jbossts.txbridge.tests.outbound.utility.TestVolatileParticipant_error_remotetrace_entry {code} The only Byteman thread in the stack dump is as follows: {code} "Thread-0" daemon prio=10 tid=0x54943000 nid=0x7686 runnable [0x548fe000] java.lang.Thread.State: RUNNABLE at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398) at java.net.ServerSocket.implAccept(ServerSocket.java:522) at java.net.ServerSocket.accept(ServerSocket.java:490) at org.jboss.byteman.agent.TransformListener.run(TransformListener.java:133) {code} > org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests Timeout (900mins) > ------------------------------------------------------------------------------------ > > Key: JBTM-1344 > URL: https://issues.jboss.org/browse/JBTM-1344 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TxBridge > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 4.17.3, 5.0.0.M2 > > > See: http://172.17.131.2/job/jbossts-narayana-java6/81/ -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1344) org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests Timeout (900mins)

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1344?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1344: ------------------------------------- Notice that it's 'basic test' that is hanging. This test does not cause a crash, which makes it simpler to figure out what's going on. The thread dump doesn't seem to show any of the TXBridge tests or code in the stack traces, so it's not clear what the test is waiting for. It's possible that we could be missing some output from the console due to Hudson not flushing the log before it was killed. Assuming we are not, the next line of output you would expect (captured from a successful run) is: {code} installing: RULE org.jboss.byteman.contrib.dtest.Instrumentor_org.jboss.jbossts.txbridge.tests.outbound.utility.TestVolatileParticipant_error_remotetrace_entry {code} The only Byteman thread in the stack dump is as follows: {code} "Thread-0" daemon prio=10 tid=0x54943000 nid=0x7686 runnable [0x548fe000] java.lang.Thread.State: RUNNABLE at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398) at java.net.ServerSocket.implAccept(ServerSocket.java:522) at java.net.ServerSocket.accept(ServerSocket.java:490) at org.jboss.byteman.agent.TransformListener.run(TransformListener.java:133) {code} > org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests Timeout (900mins) > ------------------------------------------------------------------------------------ > > Key: JBTM-1344 > URL: https://issues.jboss.org/browse/JBTM-1344 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TxBridge > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 4.17.3, 5.0.0.M2 > > > See: http://172.17.131.2/job/jbossts-narayana-java6/81/ -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1355) Merge XTS JUnit and Arquillian tests

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1355?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1355: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Merge XTS JUnit and Arquillian tests > ------------------------------------ > > Key: JBTM-1355 > URL: https://issues.jboss.org/browse/JBTM-1355 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Minor > Labels: assign > Fix For: 4.17.4, 5.0.0.M2 > > Original Estimate: 4 hours > Time Spent: 7 hours > Remaining Estimate: 0 minutes > > When migrating the XTS tests to Arquillian, we wanted to make sure that the old tests where still functional whilst the Arquillian counterparts stabilized. As a result we now have two classes for each test. The Arquillian test delegates each @Test method to the corresponding @Test in the old suite. > For example: > We have the actual test in: > ./XTS/localjunit/WSTX/src/main/java/com/arjuna/wst11/tests/arq/ba/MultiClose.java > And then a Arquillian JUnit test which just calls the test methods above is here: > ./XTS/localjunit/WSTX/src/test/java/com/arjuna/wst11/tests/arq/ba/MultiCloseTest.java > To resolve this issue, we should remove the tests under './XTS/localjunit/WSTX/src/main/java' and merge the test methods into Arquillian test. At the end of this process "./XTS/localjunit/WSTX/src/main" should be empty (and thus removed). > This applies to most, if not all suites under "./XTS/localjunit/". -- 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

13 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues January 2013