Bug 900632 (JBPAPP6-1294)
Summary: | (6.4.z) Management CLI tests (FileArgumentTestCase and CommandsArgumentTestCase) hang on Windows frequently causing EAP 6 testsuite to terminate abruptly on Windows | ||||||
---|---|---|---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Madhumita Sadhukhan <msadhukh> | ||||
Component: | CLI, Testsuite | Assignee: | jboss-set | ||||
Status: | CLOSED WONTFIX | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 6.0.0, 6.3.0 | CC: | alex, bbaranow, brian.stansberry, cdewolf, msochure, olubyans, pkremens, pslavice, rsvoboda, smcgowan | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
URL: | http://jira.jboss.org/jira/browse/JBPAPP6-1294 | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2019-03-01 12:28:38 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 900317 | ||||||
Attachments: |
|
Description
Madhumita Sadhukhan
2012-06-13 14:55:03 UTC
Attachment: Added: server.log CommandsArgumentTestCase should be fixed in the current master and 7.1. FileArgumentTestCase fix is waiting to be merged. Hi Alexey, In that case please update with correct fix version The fix has been merged into the current 7.1 branch. So, it'll appear in the next EAP release. I am not sure which one that will be. These tests do not hang anymore.FileArgumentTestCase fails on Windows even though I run Testsuite on new fast Windows machines in 6.0.1.ER2. Stacktrace java.lang.AssertionError at org.junit.Assert.fail(Assert.java:92) at org.junit.Assert.assertTrue(Assert.java:43) at org.junit.Assert.assertTrue(Assert.java:54) at org.jboss.as.test.integration.management.cli.FileArgumentTestCase.assertFailure(FileArgumentTestCase.java:125) at org.jboss.as.test.integration.management.cli.FileArgumentTestCase.testFailure(FileArgumentTestCase.java:90) These tests are all failing due to AssertionFailure and I could not find anything distinct in server-side logs. 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=dev101-W2k8r2-x86_64/lastCompletedBuild/testReport/ So, basically all tests that check java.lang.Process.exitValue() of the cli process on windows. The exit code is set in the cli process as System.exit(exitCode). The first thing check would be create a simple process, call System.exit(1) from it and check what Process.exitValue() returns on windows. Unfortunately, I don't have a windows machine here to check. Does this happen every time? The tests pass on windows on http://teamcity.cafe-babe.org. I can't test it anywhere else, atm. yes they failed in all the runs in the best windows machines we have in QE lab https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-60-as-testsuite-Windows-matrix-OracleJDK6/ Ok, thanks. It might be related to AS7-5763 Link: Added: This issue is a dependency of JBPAPP-8860 Docs QE Status: Removed: NEW FileArgumentTestCase is still failing although rarely. See: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-as-testsuite-Windows-matrix-OracleJDK7/jdk=java17_default,label_exp=w2k12r2/129/testReport/org.jboss.as.test.integration.management.cli/FileArgumentTestCase/ java.lang.AssertionError at org.junit.Assert.fail(Assert.java:86) at org.junit.Assert.assertTrue(Assert.java:41) at org.junit.Assert.assertTrue(Assert.java:52) at org.jboss.as.test.integration.management.cli.FileArgumentTestCase.assertFailure(FileArgumentTestCase.java:125) at org.jboss.as.test.integration.management.cli.FileArgumentTestCase.testFailure(FileArgumentTestCase.java:90) If the machine is restarted it never happens again.. so it can be enviromental issue. |