[jboss-jira] [JBoss JIRA] (JGRP-1740) Byteman tests fail on Windows

[Richard Achmatowicz (JIRA)]

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

Richard Achmatowicz commented on JGRP-1740:
-------------------------------------------

{noformat}
byteman:
    [mkdir] Created dir: /home/nrla/projects/jgroups-git-repo/tmp/test-results/xml/byteman
   [testng] Error opening zip file or JAR manifest missing : /home/nrla/projects/jgroups-git-repo/lib/byteman.jar
   [testng] Error occurred during initialization of VM
   [testng] agent library failed to init: instrument
   [testng] The tests failed.

BUILD SUCCESSFUL
Total time: 46 minutes 34 seconds
[nrla at lenovo jgroups-git-repo]$ ls lib
bcprov-jdk15-140.jar  byteman-bmunit-2.1.3.jar	 ivy-2.3.0.jar	     log4j-api-2.0-beta9.jar   testng-6.8.7.jar
bnd-1.50.0.jar	      byteman-install-2.1.3.jar  jcommander-1.5.jar  log4j-core-2.0-beta9.jar  xalan-2.7.1.jar
byteman-2.1.3.jar     byteman-submit-2.1.3.jar	 log4j-1.2.14.jar    serializer-2.7.1.jar

{noformat}

Did you make any provision for renaming the byteman jar?

                
> Byteman tests fail on Windows
> -----------------------------
>
>                 Key: JGRP-1740
>                 URL: https://issues.jboss.org/browse/JGRP-1740
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 3.5
>         Environment: Windows
>            Reporter: Richard Achmatowicz
>            Assignee: Bela Ban
>            Priority: Minor
>             Fix For: 3.5
>
>
> The Byteman tests in the Jgroups testsuite fail when running the testsuite on Windows. The error text is as follows:
> {noformat}
> byteman:
>    [testng] -- onStart -- byteman
>    [testng] failed config: java.io.FileNotFoundException: Rule file not found for Byteman test case org.jgroups.tests.byteman.BecomeServerTest#testSendingOfMsgsOnUnconnectedChannel
>    [testng] FAIL: [1] org.jgroups.tests.byteman.BecomeServerTest.bmngBeforeTest-Method()
>    [testng] SKIP: [1] org.jgroups.tests.byteman.BecomeServerTest.testSendingOfMsgsOnUnconnectedChannel()
>    [testng] failed config: java.io.FileNotFoundException: Rule file not found for Byteman test case org.jgroups.tests.byteman.BecomeServerTest#testSendingOfMsgsOnUnconnectedChannel
>    [testng] FAIL: [1] org.jgroups.tests.byteman.BecomeServerTest.bmngAfterTest-Method()
>    [testng] SKIP: [1] org.jgroups.tests.byteman.ForwardToCoordFailoverTest.testSendingDuringViewChange()
>    [testng] failed config: java.io.FileNotFoundException: Rule file not found for Byteman test case org.jgroups.tests.byteman.ForwardToCoordFailoverTest#testSendingDuringViewChange
>    [testng] FAIL: [1] org.jgroups.tests.byteman.ForwardToCoordFailoverTest.bmngAfterTest-Method()
>    [testng] SKIP: [1] org.jgroups.tests.byteman.MessageBeforeConnectedTest.testSendingOfMsgsOnUnconnectedChannel()
>    [testng] failed config: java.io.FileNotFoundException: Rule file not found for Byteman test case org.jgroups.tests.byteman.MessageBeforeConnectedTest#testSendingOfMsgsOnUnconnectedChannel
>    [testng] FAIL: [1] org.jgroups.tests.byteman.MessageBeforeConnectedTest.bmngAfterTest-Method()
>    [testng] SKIP: [1] org.jgroups.tests.byteman.SequencerFailoverTest.testBroadcastSequenceSenderIsB()
>    [testng] SKIP: [1] org.jgroups.tests.byteman.SequencerFailoverTest.testBroadcastSequenceSenderIsC()
>    [testng] SKIP: [1] org.jgroups.tests.byteman.SequencerFailoverTest.testFailoverWithMultipleThreadsSendingMessages()
>    [testng] SKIP: [1] org.jgroups.tests.byteman.SequencerFailoverTest.testResendingVersusNewMessages()
>    [testng] failed config: java.io.FileNotFoundException: Rule file not found for Byteman test case org.jgroups.tests.byteman.SequencerFailoverTest#testResendingVersusNewMessages
>    [testng] FAIL: [1] org.jgroups.tests.byteman.SequencerFailoverTest.bmngAfterTest-Method()
>    [testng] The tests failed.
> {noformat}

--
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