[JBoss JIRA] (WFLY-9778) Test suite is putting temporary modules in build directory
by David Lloyd (JIRA)
David Lloyd created WFLY-9778:
---------------------------------
Summary: Test suite is putting temporary modules in build directory
Key: WFLY-9778
URL: https://issues.jboss.org/browse/WFLY-9778
Project: WildFly
Issue Type: Bug
Components: Test Suite
Reporter: David Lloyd
Priority: Critical
Something (I think the test suite) is generating non-distribution-related modules into the {{build}} directory of the server, for example {{build/target/wildfly-12.0.0.Alpha1-SNAPSHOT/modules/connlistener}}. We should not be doing this; these kinds of special modules should be generated elsewhere and overlaid on the test suite images that need them.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9777) Test suite is leaving debris in git-trackable directories
by David Lloyd (JIRA)
David Lloyd created WFLY-9777:
---------------------------------
Summary: Test suite is leaving debris in git-trackable directories
Key: WFLY-9777
URL: https://issues.jboss.org/browse/WFLY-9777
Project: WildFly
Issue Type: Bug
Components: Test Suite
Reporter: David Lloyd
Priority: Critical
After a full test run, {{git status}} reports the following:
{noformat}
Untracked files:
(use "git add <file>..." to include in what will be committed)
testsuite/integration/basic/user-transaction-access-test.jar
testsuite/integration/elytron/boot.log
testsuite/integration/elytron/boot.log.2018-02-05
testsuite/integration/iiop/CosServices.cfg
testsuite/integration/iiop/ObjectStore/
testsuite/integration/ws/jaxws-samples-wsse-policy-trust-client.jar
no changes added to commit (use "git add" and/or "git commit -a")
{noformat}
This is highly problematic as it's just a matter of time before one of these files ends up getting committed by mistake.
Update the test suite to create temporary files in {{target}} directories only.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3586) Issues adding jmx to embedded host controller booted with empty config
by Ken Wills (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3586?page=com.atlassian.jira.plugi... ]
Ken Wills updated WFCORE-3586:
------------------------------
Priority: Blocker (was: Major)
> Issues adding jmx to embedded host controller booted with empty config
> ----------------------------------------------------------------------
>
> Key: WFCORE-3586
> URL: https://issues.jboss.org/browse/WFCORE-3586
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Ken Wills
> Assignee: Ken Wills
> Priority: Blocker
>
> * [domain@embedded /] /host=slave/subsystem=jmx:add
> {
> "outcome" => "failed",
> "result" => {},
> "failure-description" => {"host-failure-descriptions" => {"slave" => {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.jmx.management.integration"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.management.jmx is missing [jboss.jmx.management.integration]"]
> }}},
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9572) Speed up clustering testsuite
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9572?page=com.atlassian.jira.plugin.... ]
Radoslav Husar edited comment on WFLY-9572 at 2/8/18 10:56 AM:
---------------------------------------------------------------
All incorporated issues are resolved, resolving as partially completed since there are areas for speedup. There is a couple of follow up Jiras that will follow to expand the testsuite.
was (Author: rhusar):
All incorporated issues are resolved, there is a couple of follow up Jiras that will follow to expand the testsuite.
> Speed up clustering testsuite
> -----------------------------
>
> Key: WFLY-9572
> URL: https://issues.jboss.org/browse/WFLY-9572
> Project: WildFly
> Issue Type: Task
> Components: Clustering, Test Suite
> Affects Versions: 11.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 12.0.0.Alpha1
>
>
> Tracking issue for speeding up clustering testsuite.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3586) Issues adding jmx to embedded host controller booted with empty config
by Ken Wills (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3586?page=com.atlassian.jira.plugi... ]
Ken Wills moved CLOUD-2298 to WFCORE-3586:
------------------------------------------
Project: WildFly Core (was: Cloud Enablement)
Key: WFCORE-3586 (was: CLOUD-2298)
Workflow: GIT Pull Request workflow (was: CDW v1)
> Issues adding jmx to embedded host controller booted with empty config
> ----------------------------------------------------------------------
>
> Key: WFCORE-3586
> URL: https://issues.jboss.org/browse/WFCORE-3586
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Ken Wills
> Assignee: Ken Wills
>
> * [domain@embedded /] /host=slave/subsystem=jmx:add
> {
> "outcome" => "failed",
> "result" => {},
> "failure-description" => {"host-failure-descriptions" => {"slave" => {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.jmx.management.integration"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.management.jmx is missing [jboss.jmx.management.integration]"]
> }}},
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9775) Clustering testsuite: cleanup @RunAsClient and "testable = false"
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9775?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-9775:
---------------------------------
Summary: Clustering testsuite: cleanup @RunAsClient and "testable = false" (was: Clusterin testsuite: cleanup @RunAsClient and "testable = false")
> Clustering testsuite: cleanup @RunAsClient and "testable = false"
> -----------------------------------------------------------------
>
> Key: WFLY-9775
> URL: https://issues.jboss.org/browse/WFLY-9775
> Project: WildFly
> Issue Type: Task
> Components: Clustering, Test Suite
> Affects Versions: 11.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> None of the deployments used in the clustering tests are tested in container thus all should be marked as {{testable = false}} defining that deployment should not be wrapped up based on the protocol so the testcase can be executed incontainer. This means, there is no reason to explicitly label the test classes as {{\@RunAsClient}} since that behavior is driven by specified {{\@Deployments}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months