[jbossts-issues] [JBoss JIRA] (JBTM-1601) Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 on windows machines with jacorb

Ondřej Chaloupka (JIRA) jira-events at lists.jboss.org
Mon Apr 29 05:54:53 EDT 2013

    [ https://issues.jboss.org/browse/JBTM-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770633#comment-12770633 ] 

Ondřej Chaloupka commented on JBTM-1601:


thank you for looking at this.
The tests are passing smoothly with the redefined timeout multiplier. 

I suppose that this test could be set to 'resolved'.

> Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 on windows machines with jacorb
> --------------------------------------------------------------------------------------------------------------------
>                 Key: JBTM-1601
>                 URL: https://issues.jboss.org/browse/JBTM-1601
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Testing
>    Affects Versions: 4.17.3, 5.0.0.M2
>            Reporter: Ondřej Chaloupka
>            Assignee: Michael Musgrove
> I'm hitting an issue on qa tests for windows machines. I'm currently testing EAP 6.1.0.ER3.
> Testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 is failing when it's run on windows machines. It does not matter which JDK is used. It fails on 4.17 branch and master as well.
> This happens for jacorb.
> The fails consistently occur on 5 tests from the testcase - that are from CrashRecovery02_2_Test26 till CrashRecovery02_2_Test30.
> All of them throw assertion:
> {quote}
> junit.framework.AssertionFailedError: task client1 printed Failed.
> {quote}
> These details apply to test CrashRecovery02_2_Test27:
> The client implementation is org.jboss.jbossts.qa.CrashRecovery02.Client02a and the fail comes from line 114 (branch 4.17).
> {code}
> correct = correct && (resourceTrace1 == ResourceTrace.ResourceTraceCommit);
> {code}
> Where the value of resourceTrace1 is {{ResourceTraceNone}}.
> I didn't get with investigation further so far.
> Steps for reproducing could be handy (using narayana.sh script first):
> 1. export NARAYANA_BUILD=0
>    export NARAYANA_TESTS=0
>    export CP_NARAYANA_AS=0
>    export AS_BUILD=0
>    export XTS_AS_TESTS=0
>    export TXF_TESTS=0
>    export XTS_TESTS=0
>    export txbridge=0
>    export QA_TESTS=1
>    export SUN_ORB=0   
>    export QA_TARGET=test
>    export QA_PROFILE="-Dtest=crashrecovery02_2"   
>    export WORKSPACE=$PWD
> 2. run naryana.sh - there was problem with paths for me so the command looks like this at the end
> {quote}
> sh scripts/hudson/narayana.sh -Demma.jar.location=c:\\tmp\\ochaloup\\ext -Demma.enabled=false -Dorson.jar.location=\\tmp\\ochaloup\\ext
> {quote}
> You can check whole stacktrace from job on jenkins:
> - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTS/view/JBossTS-EAP61/job/eap-61-jbossts-qa-mswindows-test-narayana-4.17/16/consoleFull
> - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTS/view/JBossTS-EAP61/job/eap-61-jbossts-qa-mswindows-test-narayana-4.17/16/artifact/archive.zip
> Do you think that you could check this?

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

More information about the jbossts-issues mailing list