Link type: Superset, Source: JBPAPP6-1179, Destination: JBPAPP6-718 project_key: JBPAPP6 Windows testsuite which was stable in EAP6 ER3 cycle looks highly unstable with EAP6 ER6 and EAP6 ER7.There are some consistent as well as several random failures in the several runs I had started. Link for best run had so far in ER6: https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-60-as-testsuite-Windows-matrix-OracleJDK6/jdk=java16_default,label=Win2k8r2_x86_64/21/testReport/ I just noticed that the upstream job run by dev is not even testing all the tests as most tests are skipped in it dueto timeout or build failure and it still yields a yellow run!
I see many clustering tests failing often due to service jboss.jgroups.channel.web: java.lang.IllegalStateException: JBAS010272: A node named node-0 already exists in this cluster. Perhaps there is already a server running on this host? If so, restart this server with a unique node name, via -Djboss.node.name=<node-name> at org.jboss.as.clustering.msc.AsynchronousService$1.run(AsynchronousService.java:62) [jboss-as-clustering-common-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_24] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_24] Caused by: java.lang.IllegalStateException: JBAS010272: A node named node-0 already exists in this cluster. Perhaps there is already a server running on this host? If so, restart this server with a unique node name, via -Djboss.node.name=<node-name> at org.jboss.as.clustering.jgroups.subsystem.ChannelService.start(ChannelService.java:53) [jboss-as-clustering-jgroups-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1]
Link: Added: This issue depends JBPAPP-8960
With latest upstream(7.1.2.Final tag), there is only issue with SingletonService test. Others pass without any problems.
Link: Added: This issue incorporates JBPAPP-8225
Tomas could you please confirm the upstream job link for Windows? I was looking at https://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-7.1.x-testSuite-windows/lastCompletedBuild/testReport/ and found that this job skips most of the tests mainly all integration tests .
Link for best run I had with ER7 on windows run over IPv4 with mcast shows 49 test failures: http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-60-as-testsuite-Windows-matrix-OracleJDK7/17/jdk=java17_default,label=Win2k8_x86/testReport/
https://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-7.1.x-testSuite-windows/ is the right one for upstream, few tests fail here because OutOfMemmory occurred, that can be fixed by modifying the job a bit, or replacing jvm on build server running it. Eap build job looks odd as none of build have managed to run / complete build for few weeks now... it looks like last build was for ER6 but links appear right http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-60-as-testsuite-Windows-matrix-OracleJDK7/ http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-60-as-testsuite-Windows-matrix-OracleJDK6/
Tomaz, EAP jobs are maintained by myself , so I know they are correct :-) and the builds have not completed correctly because they have failed tests precisely clustering targets. If the upstream job link is correct please check that it does not run any of the integration tests at all in the last few runs.
Hi Tomas, I have run the job manually in qa lab windows machine as well as on hudson and could get rid of Clustering test failures as they passed successfully.However i still see several tests(Mostly management cli tests) failing due to Timeout even when the tests are run manually after proper clean up of all prior processes,if any on the box. With ER7 bits I found the following tests failing: org.jboss.as.test.integration.jdr.mgmt.JdrReportManagmentTestCase.generateStandaloneJdrReport(JBPAPP-8225) org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase.testProperties(JBPAPP-8963) CLI tests either failing due to Timeout or JBPAPP-8966 org.jboss.as.test.integration.management.cli.ArchiveDefaultScriptNamesTestCase.testDeployArchive org.jboss.as.test.integration.management.cli.ArchiveTestCase.testDeployArchive org.jboss.as.test.integration.management.cli.CliArgumentsTestCase.testCommandsArgument org.jboss.as.test.integration.management.cli.CliArgumentsTestCase.testConnectArgument org.jboss.as.test.integration.management.cli.MultipleLinesCommandsTestCase.testOperation org.jboss.as.test.integration.management.cli.MultipleLinesCommandsTestCase.testCommand org.jboss.as.test.integration.management.cli.BatchTestCase.org.jboss.as.test.integration.management.cli.BatchTestCase org.jboss.as.test.integration.management.cli.DataSourceTestCase.org.jboss.as.test.integration.management.cli.DataSourceTestCase org.jboss.as.test.clustering.cluster.singleton.SingletonTestCase(UDP).testSingletonService(JBPAPP-8960) Some other consistent failures I notice: org.jboss.as.test.integration.security.loginmodules.DatabaseLoginModuleTestCase org.jboss.as.test.integration.security.loginmodules.UsersRolesLoginModuleTestCase http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-60-as-testsuite-Windows-matrix-OracleJDK6/jdk=java16_default,label=Win2k8_x86/lastCompletedBuild/testReport/org.jboss.as.test.integration.security.loginmodules/UsersRolesLoginModuleTestCase/org_jboss_as_test_integration_security_loginmodules_UsersRolesLoginModuleTestCase/ fail with following stacktrace: java.lang.RuntimeException: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.spec.WebArchive org.jboss.as.test.integration.security.loginmodules.UsersRolesLoginModuleTestCase.appDeployment1() at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.invoke(AnnotationDeploymentScenarioGenerator.java:160) at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generateDeployment(AnnotationDeploymentScenarioGenerator.java:94) Apart from these there are several unstable/inconsistent failures due to serbver not running or Connection Closed. This result is as per ER7 bits .Please update jira with details of which of the above failures(consistent failures at least) have been fixed in ER8 and set the jira to correct fix version if above issues are resolved. FYI... the latest upstream job http://hudson.jboss.org/hudson/view/All/job/JBoss-AS-7.1.x-testSuite-windows/1219/testReport/ is still not running any of the integration tests at all so its hard to determine which of the tests are actually fixed!
org.jboss.as.test.integration.security.loginmodules.DatabaseLoginModuleTestCase. fails consistently on Windows environment with EAP6 ER8 run against node0 and node1 with mcast with stacktrace attached (check integration.security.loginmodules.DatabaseLoginModuleTestCase.log)
Attachment: Added: integration.security.loginmodules.DatabaseLoginModuleTestCase.log
Fix for JBPAPP-8960 was pushed to 7.1.x upstream
Tomas I still see it failing in EAP6 CR1 please make sure you mark the correct fix version in JBPAPP-8960 once this changed is picked up in EAP from upstream.
Link: Added: This issue is a dependency of JBPAPP-9188
There are some more fixes for this issue, some of them are already in upstream, for few pull request was sent, and there are still some fixes in work.
The DatabaseLoginModuleTestCase and UsersRolesLoginModuleTestCase were updated in both master and 7.1 AS branches. They should work now. Madhumita, could you please retry it? Thanks.
Link: Added: This issue depends AS7-5350
Testsuite on windows now only has one more failure which is described in AS7-5350
Agreed,I have run with unofficial build from productization taken from upstream that shows 5 failures(4 of which also fail on RHEL and other platforms) and fifth failure is CliArgumentsTestCase.testWrongControler.This run also verifies that security tests failing in GA and fixed by Josef are passing. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP5/view/JDK7/job/eap-601-CI-as-testsuite-Win2k8R2_x86_64-OracleJDK6-srczip/15/testReport/ However I see following in my run above as well as in the upstream windows job: org.jboss.as.test.clustering.cluster.singleton.SingletonTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.001 sec @Tomas fyi...this was a bug in GA and this test has been skipped.(probably it is still failing?)
Link: Added: This issue relates to AS7-5210
Link: Removed: This issue relates to AS7-5210
Link: Added: This issue depends AS7-5210
SingletonTestCase was fixed in upstream some time ago, but after 6.0.0.GA. there are issues in upstream on JDK7, and there is plan to fix all that issues before 7.2.0.final is released. I would recommend you to use JDK6 for all test runs. this is upstream master testsuite: http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-windows-build/lastCompletedBuild/testReport/ and for 7.1 branch EAP 6.0.x upstream http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-windows-build/lastCompletedBuild/testReport/ classloader leak tests ware fixed week or two ago, so probably where the EAP is rebased to master it should be fixed.
Thanks Tomas , however SingletonTestCase has been skipped in the upstram master testsuite(in link provided by you above this particular testcase has been skipped and not run) so its definitely not fixed yet:-) But I found AS7-5210 and it says it has been deferred to 7.2 (the test is not currently run at all in testsuite so we do not know if it fails or passes)
Please retest against EAP 6.0.1 and either re-open or create a new jira if the issues still exists.
Re-opening this as there are associated unresolved jiras
Link: Added: This issue depends JBPAPP-10033
Link: Added: This issue depends JBPAPP-10101
Link: Added: This issue depends JBPAPP-9335
Release Notes Docs Status: Added: Not Required
Release Notes Docs Status: Removed: Not Required Docs QE Status: Removed: NEW
As of EAP 6.0.1.ER4.1 the failures still exist as reported in associated jiras. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-60-as-testsuite-Windows-matrix-OracleJDK6/jdk=java16_default,label=vmg44-w2k8r2-x86_64/lastCompletedBuild/testReport/
This is tracker jira for all Windows test failures so assigning this to Pavel Jelinek for tracking during my absence.Pavel please check all associated jiras on which this issue depends on before verifying or closing this.
This was fixed some time ago, and should already be part of EAP 6.1
This was fixed some time ago, testsuite passes on windows for some time now.