Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[WFCORE-6972] The standard configuration files used for testsuite/domain should not include community namespaces. #6207

Merged
merged 2 commits into from
Oct 2, 2024
Merged

[WFCORE-6972] The standard configuration files used for testsuite/domain should not include community namespaces. #6207

merged 2 commits into from
Oct 2, 2024

Conversation

ehsavoie
Copy link
Contributor

@ehsavoie ehsavoie commented Sep 30, 2024 •
edited
Loading

The use of namespaces for lower stability levels should be reserved for
stability level specific tests.

Jira: https://issues.redhat.com/browse/WFCORE-6972

@darranl @ehsavoie
[WFCORE-6972] The standard configuration files used for testsuite/dom…
efa4443 
…ain should not include community namespaces.

The use of namespaces for lower stability levels should be reserved for
stability level specific tests.
@ehsavoie ehsavoie changed the title Wfcore 6972 [WFCORE-6972] The standard configuration files used for testsuite/domain should not include community namespaces. Sep 30, 2024
@ehsavoie
Copy link
Contributor Author

Should supersede #6153

@wildfly-ci

This comment was marked as outdated.

Sign in to view
@ehsavoie
[WFCORE-6972]: Fixing the tests to support community schemas
7b82390 
Signed-off-by: Emmanuel Hugonnet <ehugonne@redhat.com>
@wildfly-ci

This comment was marked as off-topic.

Sign in to view
@wildfly-ci

This comment was marked as off-topic.

Sign in to view
@wildfly-ci
Copy link

Core -> Full Integration Build 13965 outcome was FAILURE using a merge of 7b82390
Summary: Tests failed: 1 (1 new), passed: 3989, ignored: 59 Build time: 02:03:10

Failed tests

org.jboss.as.test.clustering.cluster.ejb.timer.DistributedTimerServiceTestCase.test: java.lang.AssertionError: class org.jboss.as.test.clustering.cluster.ejb.timer.beans.CalendarPersistentTimerBean={node-1=[]}. Actual: 0
	at org.jboss.as.test.clustering.cluster.ejb.timer.AbstractTimerServiceTestCase.test(AbstractTimerServiceTestCase.java:305)
	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 jdk.internal.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at jdk.internal.reflect.GeneratedMethodAccessor26.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at jdk.internal.reflect.GeneratedMethodAccessor25.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at jdk.internal.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at jdk.internal.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at jdk.internal.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at jdk.internal.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at jdk.internal.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at jdk.internal.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
------- Stdout: -------
node-2 2024-10-02 09:35:12,263 INFO  [org.jboss.modules] (main) JBoss Modules version 2.1.5.Final
node-2 2024-10-02 09:35:12,786 INFO  [org.jboss.msc] (main) JBoss MSC version 1.5.5.Final
node-2 2024-10-02 09:35:12,799 INFO  [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final
node-2 2024-10-02 09:35:12,915 INFO  [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly 34.0.0.Final-SNAPSHOT (WildFly Core 26.0.0.Beta6-SNAPSHOT) starting
node-2 2024-10-02 09:35:14,422 INFO  [org.wildfly.security] (Controller Boot Thread) ELY00001: WildFly Elytron version 2.6.0.Final
node-2 2024-10-02 09:35:15,387 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
node-2 2024-10-02 09:35:15,409 INFO  [org.xnio] (MSC service thread 1-1) XNIO version 3.8.16.Final
node-2 2024-10-02 09:35:15,416 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.8.16.Final
node-2 2024-10-02 09:35:15,485 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 5.0.29.Final
node-2 2024-10-02 09:35:15,506 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 40) WFLYCLINF0001: Activating Infinispan subsystem.
node-2 2024-10-02 09:35:15,529 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 48) WFLYNAM0001: Activating Naming Subsystem
node-2 2024-10-02 09:35:15,553 INFO  [org.jboss.as.naming] (MSC service thread 1-3) WFLYNAM0003: Starting Naming Service
node-2 2024-10-02 09:35:15,581 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 42) WFLYRS0016: RESTEasy version 6.2.10.Final
node-2 2024-10-02 09:35:15,560 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 44) WFLYCLJG0001: Activating JGroups subsystem. JGroups version 5.2.28
node-2 2024-10-02 09:35:15,590 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 53) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
node-2 2024-10-02 09:35:15,630 INFO  [org.jboss.as.connector] (MSC service thread 1-3) WFLYJCA0009: Starting Jakarta Connectors Subsystem (WildFly/IronJacamar 3.0.10.Final)
node-2 2024-10-02 09:35:15,661 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 41) WFLYIO001: Worker 'default' has auto-configured to 8 IO threads with 64 max task threads based on your 4 available processors
node-2 2024-10-02 09:35:15,670 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 32) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 2.2)
node-2 2024-10-02 09:35:15,725 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0003: Undertow 2.3.17.Final starting
node-2 2024-10-02 09:35:15,726 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = h2
node-2 2024-10-02 09:35:15,796 WARN  [org.wildfly.extension.elytron] (MSC service thread 1-8) WFLYELY00023: KeyStore file '/opt/buildAgent/work/e8e0dd9c7c4ba60/full/testsuite/integration/clustering/target/wildfly-clustering-ejb-2/standalone/configuration/application.keystore' does not exist. Used blank.
node-2 2024-10-02 09:35:15,826 INFO  [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
node-2 2024-10-02 09:35:15,826 INFO  [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.

@yersan yersan added the ready-for-merge This PR is ready to be merged and fulfills all requirements label Oct 2, 2024
@yersan yersan merged commit 205e257 into wildfly:main Oct 2, 2024
10 of 13 checks passed
@yersan
Copy link
Collaborator

yersan commented Oct 2, 2024

Thanks @ehsavoie @darranl

@yersan yersan mentioned this pull request Oct 2, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@yersan yersan yersan approved these changes

@darranl darranl Awaiting requested review from darranl

Assignees
No one assigned
Labels
ready-for-merge This PR is ready to be merged and fulfills all requirements
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@ehsavoie @wildfly-ci @yersan @darranl