]
Yeray Borges Santana updated WFLY-14282:
----------------------------------------
Steps to Reproduce:
$ cd wildfly/testsuite/domain
$ mvn clean install \-Dtest=HostExcludesTestCase \-DtestLogToFile=false
\-Dtestsuite.default.build.project.prefix=ee\-
was:
$ cd wildfly/testsuite/domain
$ mvn clean install -Dtest=HostExcludesTestCase -DtestLogToFile=false
-Dtestsuite.default.build.project.prefix=ee-
HostExcludesTestCase.testHostExcludes fails with
wildfly-ee-galleon-pack server distribution
--------------------------------------------------------------------------------------------
Key: WFLY-14282
URL:
https://issues.redhat.com/browse/WFLY-14282
Project: WildFly
Issue Type: Bug
Components: Test Suite
Reporter: Yeray Borges Santana
Assignee: Yeray Borges Santana
Priority: Minor
HostExcludesTestCase.testHostExcludes verifies the host exclusions configuration. When
this test is executed on a server built by using the wildfly-ee-galleon-pack it fails with
the following error:
{noformat}
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.202 s
<<< FAILURE! - in org.jboss.as.test.integration.domain.HostExcludesTestCase
[ERROR] testHostExcludes(org.jboss.as.test.integration.domain.HostExcludesTestCase) Time
elapsed: 1.039 s <<< FAILURE!
java.lang.AssertionError: These exclusions are not required for WildFly14.0 host-exclude:
[org.wildfly.extension.microprofile.opentracing-smallrye,
org.wildfly.extension.microprofile.health-smallrye,
org.wildfly.extension.microprofile.config-smallrye]
at org.junit.Assert.fail(Assert.java:89)
at
org.jboss.as.test.integration.domain.HostExcludesTestCase.testHostExcludes(HostExcludesTestCase.java:375)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
{noformat}
The error can be considered as just noise because it is not problematic to have
unrequited exclusions. We have either fix the test to be less restrictive or clean the
unneeded exclusions from the configuration since they are unrequired