[jboss-jira] [JBoss JIRA] (WFLY-5696) Mixed domain test launches a broken server from the DC
Brian Stansberry (JIRA)
issues at jboss.org
Tue Nov 17 14:12:00 EST 2015
[ https://issues.jboss.org/browse/WFLY-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry updated WFLY-5696:
-----------------------------------
Description:
The host.xml used by the DC in the testsuite/mixed-domain tests is launching a server. This server fails to launch because the profiles being used include stuff that won't work on current version servers (i.e. legacy subsystems like web).
The failure to launch the server isn't affecting the test results, proving the existence of the server is not relevant to the test assertions.
However, WildcardReadsTestCase is asserting that the wildcard reads are able to read this server, so we need to decide how to proceed. Simply dropping the "server" element from host.xml doesn't work.
was:
The host.xml used by the DC in the testsuite/mixed-domain tests is launching a server. This server fails to launch because the profiles being used include stuff that won't work on current version servers (i.e. legacy subsystems like web).
The failure to launch the server isn't affecting the test results, proving the existence of the server is not relevant to the test assertions.
Our goal in these tests is to test how the old slaves handle stuff. We have other ways to test how new servers handle old stuff. So I'm going to remove the launch of this server from the DC config.
> Mixed domain test launches a broken server from the DC
> ------------------------------------------------------
>
> Key: WFLY-5696
> URL: https://issues.jboss.org/browse/WFLY-5696
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, Test Suite
> Affects Versions: 10.0.0.CR4
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Minor
> Fix For: 11.0.0.Alpha1
>
>
> The host.xml used by the DC in the testsuite/mixed-domain tests is launching a server. This server fails to launch because the profiles being used include stuff that won't work on current version servers (i.e. legacy subsystems like web).
> The failure to launch the server isn't affecting the test results, proving the existence of the server is not relevant to the test assertions.
> However, WildcardReadsTestCase is asserting that the wildcard reads are able to read this server, so we need to decide how to proceed. Simply dropping the "server" element from host.xml doesn't work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list