[WFCORE-3901] Remove wildfly-openssl-solaris-sparcv9 lincense

This PR follows up https://github.com/wildfly/wildfly-core/pull/3208
From the point of view of distribution created by the feature pack, the wildfly-openssl-solaris-sparcv9 is not included in the final license, but since the library was removed, it looks like it makes sense remove the license as well.
Jira issue: https://issues.jboss.org/browse/WFCORE-3901

Core - Full Integration Build 7493 outcome was FAILURE using a merge of a95503c15dcb41ea546fe4a94fc09f4f4ca913f8
Summary: Tests failed: 8 (7 new), passed: 4334, ignored: 142 Build time: 01:56:02
Failed tests
org.jboss.as.test.clustering.cluster.singleton.SingletonServiceTestCase.testSingletonService: 	at org.jboss.as.test.clustering.cluster.singleton.SingletonServiceTestCase.testSingletonService(SingletonServiceTestCase.java:232)
------- Stdout: -------
 [0m03:48:06,618 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/fa/6d5d0de4b27ffa5f19da778fac32ef56a0912b/content
 [0m [0m03:48:06,620 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "SingletonServiceTestCase.war" (runtime-name: "SingletonServiceTestCase.war")
 [0m [33m03:48:06,709 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.SingletonServiceTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [0m03:48:06,770 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) WFLYCLINF0002: Started default cache from server container
 [0m [33m03:48:06,785 WARN  [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0006: Failed to reach quorum of 2 for jboss.test.service.quorum service. No singleton master will be elected.
 [0m [0m03:48:06,787 INFO  [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0003: node-1 elected as the singleton provider of the jboss.test.service.default service
 [0m [0m03:48:06,795 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 31) WFLYUT0021: Registered web context: '/SingletonServiceTestCase' for server 'default-server'
 [0m [0m03:48:06,848 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "SingletonServiceTestCase.war" (runtime-name : "SingletonServiceTestCase.war")
 [0m [0m03:48:06,876 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/fa/6d5d0de4b27ffa5f19da778fac32ef56a0912b/content
 [0m [0m03:48:06,883 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "SingletonServiceTestCase.war" (runtime-name: "SingletonServiceTestCase.war")
 [0m [0m03:48:06,897 INFO  [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0001: This node will now operate as the singleton provider of the jboss.test.service.default service
 [0m [33m03:48:07,015 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.SingletonServiceTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [0m03:48:07,092 INFO  [org.infinispan.CLUSTER] (remote-thread--p7-t2) ISPN000310: Starting cluster-wide rebalance for cache default, topology CacheTopology{id=2, phase=READ_OLD_WRITE_ALL, rebalanceId=2, currentCH=ReplicatedConsistentHash{ns = 256, owners = (1)[node-1: 256]}, pendingCH=ReplicatedConsistentHash{ns = 256, owners = (2)[node-1: 123, node-2: 133]}, unionCH=null, actualMembers=[node-1, node-2], persistentUUIDs=[fecd0a79-0aca-4cc3-9520-faefdcb7a8f8, 80fb0e74-6889-42ca-a4fc-4a157b05dcdf]}
 [0m [0m03:48:07,093 INFO  [org.infinispan.CLUSTER] (remote-thread--p7-t2) [Context=default][Scope=node-1]ISPN100002: Started rebalance with topology id 2
 [0m [0m03:48:07,099 INFO  [org.infinispan.CLUSTER] (transport-thread--p16-t1) [Context=default][Scope=node-1]ISPN100003: Node node-1 finished rebalance phase with topology id 2
 [0m [0m03:48:07,121 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 15) WFLYUT0021: Registered web context: '/SingletonServiceTestCase' for server 'default-server'
 [0m [0m03:48:07,145 INFO  [org.infinispan.CLUSTER] (remote-thread--p7-t2) [Context=default][Scope=node-2]ISPN100003: Node node-2 finished rebalance phase with topology id 2
 [0m [0m03:48:07,146 INFO  [org.infinispan.CLUSTER] (remote-thread--p7-t2) ISPN000336: Finished cluster-wide rebalance for cache default, topology id = 2
 [0m [0m03:48:07,148 INFO  [org.infinispan.CLUSTER] (transport-thread--p16-t4) [Context=default][Scope=node-1]ISPN100003: Node node-1 finished rebalance phase with topology id 3
 [0m [0m03:48:07,153 INFO  [org.infinispan.CLUSTER] (remote-thread--p7-t2) [Context=default][Scope=node-2]ISPN100003: Node node-2 finished rebalance phase with topology id 3
 [0m [0m03:48:07,155 INFO  [org.infinispan.CLUSTER] (transport-thread--p16-t6) [Context=default][Scope=node-1]ISPN100003: Node node-1 finished rebalance phase with topology id 4
 [0m [0m03:48:07,157 INFO  [org.infinispan.CLUSTER] (remote-thread--p7-t2) [Context=default][Scope=node-2]ISPN100003: Node node-2 finished rebalance phase with topology id 4
 [0m [0m03:48:07,162 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 21) WFLYCLINF0002: Started default cache from server container
 [0m [0m03:48:07,185 INFO  [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0007: Just reached required quorum of 2 for jboss.test.service.quorum service. If this cluster loses another member, no node will be chosen to provide this service.
 [0m [0m03:48:07,186 INFO  [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0003: node-2 elected as the singleton provider of the jboss.test.service.quorum service
 [0m [0m03:48:07,190 INFO  [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0003: node-2 elected as the singleton provider of the jboss.test.service.default service
 [0m [0m03:48:07,190 INFO  [org.wildfly.clustering.server] (ChannelCommandDispatcherFactory - 2) WFLYCLSV0001: This node will now operate as the singleton provider of the jboss.test.service.quorum service
 [0m [0m03:48:07,196 INFO  [org.wildfly.clustering.server] (ChannelCommandDispatcherFactory - 1) WFLYCLSV0002: This node will no longer operate as the singleton provider of the jboss.test.service.default service
 [0m [0m03:48:07,200 INFO  [org.wildfly.clustering.server] (ChannelCommandDispatcherFactory - 2) WFLYCLSV0001: This node will now operate as the singleton provider of the jboss.test.service.default service
 [0m [0m03:48:07,210 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "SingletonServiceTestCase.war" (runtime-name : "SingletonServiceTestCase.war")
 [0m [0m03:48:07,232 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0236: Suspending server with no timeout.
 [0m [0m03:48:07,234 INFO  [org.jboss.as.ejb3] (management-handler-thread - 1) WFLYEJB0493: EJB subsystem suspension complete
 [0m [0m03:48:07,235 INFO  [org.jboss.as.server] (Management Triggered Shutdown) WFLYSRV0241: Shutting down in response to management operation 'shutdown'
 [0m [0m03:48:07,275 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 11) WFLYUT0022: Unregistered web context: '/SingletonServiceTestCase' from server 'default-server'
 [0m [0m03:48:07,288 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000080: Disconnecting JGroups channel ejb
 [0m [0m03:48:07,290 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000080: Disconnecting JGroups channel ejb
 [0m [0m03:48:07,305 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0019: Host default-host stopping
 [0m [0m03:48:07,307 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 11) MODCLUSTER000002: Initiating mod_cluster shutdown
 [0m [0m03:48:07,308 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
 [0m [0m03:48:07,310 INFO  [org.wildfly.clustering.server] (ChannelCommandDispatcherFactory - 2) WFLYCLSV0002: This node will no longer operate as the singleton provider of the jboss.test.service.default service
 [0m [0m03:48:07,310 INFO  [org.wildfly.clustering.server] (ChannelCommandDispatcherFactory - 2) WFLYCLSV0002: This node will no longer operate as the singleton provider of the jboss.test.service.quorum service
 [0m [33m03:48:07,307 WARN  [org.jboss.modcluster] (ServerService Thread Pool -- 11) MODCLUSTER000033: Failed to interrupt socket reception.: java.io.IOException: Invalid argument (sendto failed)
	at java.net.PlainDatagramSocketImpl.send(Native Method)
	at java.net.DatagramSocket.send(DatagramSocket.java:693)
	at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.interruptDatagramReader(AdvertiseListenerImpl.java:209)
	at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.stop(AdvertiseListenerImpl.java:228)
	at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.destroy(AdvertiseListenerImpl.java:244)
	at org.jboss.modcluster.ModClusterService.shutdown(ModClusterService.java:216)
	at org.wildfly.extension.mod_cluster.ContainerEventHandlerService.stop(ContainerEventHandlerService.java:69)

org.jboss.as.test.clustering.cluster.web.DistributableTestCase.testSessionReplication: java.lang.AssertionError: expected:<3> but was:<1>
	at org.jboss.as.test.clustering.cluster.web.DistributableTestCase.testSessionReplication(DistributableTestCase.java:153)
------- Stdout: -------
 [0m03:48:51,175 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/50/6e81edefe89067d49bb52051e13e11475070af/content
 [0m [0m03:48:51,177 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "DistributableTestCase.war" (runtime-name: "DistributableTestCase.war")
 [0m [0m03:48:51,273 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 78) WFLYCLINF0002: Started default-server cache from web container
 [0m [0m03:48:51,274 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 77) WFLYCLINF0002: Started DistributableTestCase.war cache from web container
 [0m [0m03:48:51,287 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 77) WFLYUT0021: Registered web context: '/DistributableTestCase' for server 'default-server'
 [0m [0m03:48:51,298 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "DistributableTestCase.war" (runtime-name : "DistributableTestCase.war")
 [0m [0m03:48:51,316 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/50/6e81edefe89067d49bb52051e13e11475070af/content
 [0m [0m03:48:51,324 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "DistributableTestCase.war" (runtime-name: "DistributableTestCase.war")
 [0m [0m03:48:51,452 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 78) WFLYCLINF0002: Started default-server cache from web container
 [0m [0m03:48:51,467 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 77) WFLYCLINF0002: Started DistributableTestCase.war cache from web container
 [0m [0m03:48:51,476 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 77) WFLYUT0021: Registered web context: '/DistributableTestCase' for server 'default-server'
 [0m [0m03:48:51,486 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "DistributableTestCase.war" (runtime-name : "DistributableTestCase.war")
 [0m [0m03:48:51,501 INFO  [io.undertow.servlet] (default task-2) /DistributableTestCase/simple, value = 1
 [0m [0m03:48:51,505 INFO  [io.undertow.servlet] (default task-1) /DistributableTestCase/simple, value = 2
 [0m [0m03:48:54,567 INFO  [io.undertow.servlet] (default task-2) /DistributableTestCase/simple, value = 1
 [0m [0m03:48:54,581 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 78) WFLYUT0022: Unregistered web context: '/DistributableTestCase' from server 'default-server'
 [0m [0m03:48:54,604 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 78) ISPN000029: Passivating all entries to disk
 [0m [0m03:48:54,608 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 78) ISPN000030: Passivated 3 entries in 4 milliseconds
 [0m [0m03:48:54,613 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 78) WFLYCLINF0003: Stopped DistributableTestCase.war cache from web container
 [0m [0m03:48:54,628 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 78) WFLYCLINF0003: Stopped default-server cache from web container
 [0m [0m03:48:54,651 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment DistributableTestCase.war (runtime-name: DistributableTestCase.war) in 74ms
 [0m [0m03:48:54,676 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0002: Content removed from location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/50/6e81edefe89067d49bb52051e13e11475070af/content
 [0m [0m03:48:54,677 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0009: Undeployed "DistributableTestCase.war" (runtime-name: "DistributableTestCase.war")
 [0m [0m03:48:54,685 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 78) WFLYUT0022: Unregistered web context: '/DistributableTestCase' from server 'default-server'
 [0m [0m03:48:54,708 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 78) ISPN000029: Passivating all entries to disk
 [0m [0m03:48:54,716 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 78) ISPN000030: Passivated 3 entries in 8 milliseconds
 [0m [0m03:48:54,721 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 78) WFLYCLINF0003: Stopped DistributableTestCase.war cache from web container
 [0m [0m03:48:54,736 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 78) WFLYCLINF0003: Stopped default-server cache from web container
 [0m [0m03:48:54,749 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment DistributableTestCase.war (runtime-name: DistributableTestCase.war) in 65ms
 [0m [0m03:48:54,777 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0002: Content removed from location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalon

org.jboss.as.test.clustering.cluster.web.CoarseWebFailoverTestCase.test: java.lang.AssertionError: expected:<200> but was:<500>
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:69)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:58)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:52)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.establishTopology(AbstractWebFailoverTestCase.java:360)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:120)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:112)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.test(AbstractWebFailoverTestCase.java:103)
------- Stdout: -------
 [0m03:49:23,248 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/a2/05314005f19468606ba15efbaf0a90e74db1ed/content
 [0m [0m03:49:23,251 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "CoarseWebFailoverTestCase.war" (runtime-name: "CoarseWebFailoverTestCase.war")
 [0m [33m03:49:23,365 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m03:49:23,366 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m03:49:23,366 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m03:49:23,366 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m03:49:23,366 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m03:49:23,396 INFO  [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment CoarseWebFailoverTestCase.war
 [0m [0m03:49:23,450 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-8) HV000001: Hibernate Validator 5.3.6.Final
 [0m [0m03:49:23,529 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "CoarseWebFailoverTestCase.war"' are as follows:

	java:global/CoarseWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/CoarseWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/CoarseWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	ejb:CoarseWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:global/CoarseWebFailoverTestCase/TopologyChangeListenerBean
	java:app/CoarseWebFailoverTestCase/TopologyChangeListenerBean
	java:module/TopologyChangeListenerBean

 [0m [0m03:49:23,666 INFO  [org.jboss.weld.Version] (MSC service thread 1-8) WELD-000900: 3.0.4 (Final)
 [0m [0m03:49:23,769 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 24) WFLYCLINF0002: Started CoarseWebFailoverTestCase.war cache from web container
 [0m [0m03:49:23,805 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 4) WFLYCLINF0002: Started default-server cache from web container
 [0m [33m03:49:24,016 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-5) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1!
 [0m [33m03:49:24,055 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-5) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor is deprecated from CDI 1.1!
 [0m [0m03:49:24,707 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 24) WFLYUT0021: Registered web context: '/CoarseWebFailoverTestCase' for server 'default-server'
 [0m [0m03:49:24,759 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "CoarseWebFailoverTestCase.war" (runtime-name : "CoarseWebFailoverTestCase.war")
 [0m [0m03:49:24,977 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/c4/afce3371b8687b873deb47101c90d6cf7dbfdd/content
 [0m [0m03:49:24,980 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "CoarseWebFailoverTestCase.war" (runtime-name: "CoarseWebFailoverTestCase.war")
 [0m [33m03:49:25,030 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m03:49:25,031 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m03:49:25,031 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m03:49:25,031 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m03:49:25,031 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.CoarseWebFailoverTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m03:49:25,035 INFO  [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment CoarseWebFailoverTestCase.war
 [0m [0m03:49:25,052 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "CoarseWebFailoverTestCase.war"' are as follows:

	java:global/CoarseWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/CoarseWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/CoarseWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	ejb:CoarseWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener

org.jboss.as.test.clustering.cluster.web.FineWebFailoverTestCase.test: java.lang.AssertionError: expected:<200> but was:<500>
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:69)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:58)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:52)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.establishTopology(AbstractWebFailoverTestCase.java:360)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:120)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:112)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.test(AbstractWebFailoverTestCase.java:103)
------- Stdout: -------
 [0m03:49:55,914 INFO  [org.jboss.modules] (main) JBoss Modules version 1.8.5.Final
 [0m [0m03:49:56,328 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.2.Final
 [0m [0m03:49:56,343 INFO  [org.jboss.threads] (main) JBoss Threads version 2.3.2.Final
 [0m [0m03:49:56,514 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 14.0.0.Beta1-SNAPSHOT (WildFly Core 6.0.0.Alpha1-SNAPSHOT) starting
 [0m [0m03:49:58,359 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m03:49:58,417 INFO  [org.wildfly.security] (ServerService Thread Pool -- 34) ELY00001: WildFly Elytron version 1.3.3.Final
 [0m [0m03:49:58,422 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 9) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 [0m [0m03:49:58,563 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
 [0m [0m03:49:58,582 INFO  [org.xnio] (MSC service thread 1-8) XNIO version 3.6.3.Final
 [0m [0m03:49:58,590 INFO  [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.6.3.Final
 [0m [0m03:49:58,623 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 48) WFLYCLINF0001: Activating Infinispan subsystem.
 [0m [0m03:49:58,628 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 49) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
 [0m [0m03:49:58,634 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 50) WFLYRS0016: RESTEasy version 3.5.1.Final
 [0m [0m03:49:58,662 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 56) WFLYJSF0007: Activated the following JSF Implementations: [main]
 [0m [0m03:49:58,678 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 53) WFLYCLJG0001: Activating JGroups subsystem. JGroups version 4.0.11
 [0m [0m03:49:58,694 INFO  [org.jboss.as.ee] (ServerService Thread Pool -- 44) WFLYEE0119: The system property 'ee8.preview.mode' is NOT set to 'true'. For provided EE 8 APIs where the EE 8 version of the API differs from what is supported in EE 7, the EE 7 variant of the API will be used. Support for this setting will be removed once all EE 8 APIs are provided and certified.
 [0m [33m03:49:58,732 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 68) 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.
 [0m [0m03:49:58,734 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 70) WFLYWS0002: Activating WebServices Extension
 [0m [0m03:49:58,740 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 65) WFLYSEC0002: Activating Security Subsystem
 [0m [0m03:49:58,746 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0003: Undertow 2.0.9.Final starting
 [0m [0m03:49:58,800 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 59) WFLYNAM0001: Activating Naming Subsystem
 [0m [0m03:49:58,804 INFO  [org.jboss.as.security] (MSC service thread 1-3) WFLYSEC0001: Current PicketBox version=5.0.2.Final
 [0m [0m03:49:58,851 INFO  [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.9.Final)
 [0m [0m03:49:58,857 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 41) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
 [0m [0m03:49:58,868 INFO  [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 5.0.7.Final
 [0m [0m03:49:58,895 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0018: Started Driver service with driver-name = h2
 [0m [0m03:49:58,909 INFO  [org.jboss.as.ejb3] (MSC service thread 1-6) 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.
 [0m [0m03:49:58,910 INFO  [org.jboss.as.ejb3] (MSC service thread 1-7) 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.
 [0m [0m03:49:59,039 INFO  [org.jboss.as.naming] (MSC service thread 1-8) WFLYNAM0003: Starting Naming Service
 [0m [0m03:49:59,044 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
 [0m [0m03:49:59,139 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 69) WFLYUT0014: Creating file handler for path '/store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
 [0m [0m03:49:59,176 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0012: Started server default-server.
 [0m [0m03:49:59,183 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0018: Host default-host starting
 [0m [0m03:49:59,231 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow AJP listener ajp listening on [::1]:8009
 [0m [0m03:49:59,233 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on [::1]:8080
 [0m [0m03:49:59,240 INFO  [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0493: EJB subsystem suspension complete
 [0m [0m03:49:59,277 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 72) MODCLUSTER000001: Initializing mod_cluster version 1.3.9.Final
 [0m [0m03:49:59,295 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 72) MODCLUSTER000032: Listening to proxy advertisements on /<IP_ADDRESS>:23364
 [0m [0m03:49:59,389 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
 [0m [0m03:49:59,395 INFO  [org.jboss.as.patching] (MSC service thread 1-7) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
 [0m [33m03:49:59,428 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
 [0m [0m03:49:59,441 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) WFLYDS0013: Started FileSystemDeploymentService for directory /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/deployments

org.jboss.as.test.clustering.cluster.web.ExternalizerTestCase.test: java.lang.AssertionError: expected:<3> but was:<1>
	at org.jboss.as.test.clustering.cluster.web.ExternalizerTestCase.assertValue(ExternalizerTestCase.java:108)
	at org.jboss.as.test.clustering.cluster.web.ExternalizerTestCase.test(ExternalizerTestCase.java:96)
------- Stdout: -------
 [0m03:50:19,927 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/13/520370af6a4cc1f4173307336dde9f7fa5b6b0/content
 [0m [0m03:50:19,935 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "ExternalizerTestCase.war" (runtime-name: "ExternalizerTestCase.war")
 [0m [0m03:50:20,130 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 17) WFLYCLINF0002: Started default-server cache from web container
 [0m [0m03:50:20,146 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 17) WFLYCLINF0002: Started ExternalizerTestCase.war cache from web container
 [0m [0m03:50:20,157 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 17) WFLYUT0021: Registered web context: '/ExternalizerTestCase' for server 'default-server'
 [0m [0m03:50:20,181 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "ExternalizerTestCase.war" (runtime-name : "ExternalizerTestCase.war")
 [0m [0m03:50:20,206 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/b9/7ff7d8cfdb2efd79ffe08848debdc7d53d8316/content
 [0m [0m03:50:20,208 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "ExternalizerTestCase.war" (runtime-name: "ExternalizerTestCase.war")
 [0m [0m03:50:20,333 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 88) WFLYCLINF0002: Started ExternalizerTestCase.war cache from web container
 [0m [0m03:50:20,337 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 86) WFLYCLINF0002: Started default-server cache from web container
 [0m [0m03:50:20,354 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 86) WFLYUT0021: Registered web context: '/ExternalizerTestCase' for server 'default-server'
 [0m [0m03:50:20,370 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "ExternalizerTestCase.war" (runtime-name : "ExternalizerTestCase.war")
 [0m [0m03:50:20,492 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 17) WFLYUT0022: Unregistered web context: '/ExternalizerTestCase' from server 'default-server'
 [0m [0m03:50:20,499 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 17) ISPN000029: Passivating all entries to disk
 [0m [0m03:50:20,502 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 17) ISPN000030: Passivated 3 entries in 3 milliseconds
 [0m [0m03:50:20,504 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 17) WFLYCLINF0003: Stopped ExternalizerTestCase.war cache from web container
 [0m [0m03:50:20,521 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 17) WFLYCLINF0003: Stopped default-server cache from web container
 [0m [0m03:50:20,537 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment ExternalizerTestCase.war (runtime-name: ExternalizerTestCase.war) in 45ms
 [0m [0m03:50:20,559 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0002: Content removed from location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/13/520370af6a4cc1f4173307336dde9f7fa5b6b0/content
 [0m [0m03:50:20,559 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0009: Undeployed "ExternalizerTestCase.war" (runtime-name: "ExternalizerTestCase.war")
 [0m [0m03:50:20,569 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 88) WFLYUT0022: Unregistered web context: '/ExternalizerTestCase' from server 'default-server'
 [0m [0m03:50:20,589 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 86) ISPN000029: Passivating all entries to disk
 [0m [0m03:50:20,591 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 86) ISPN000030: Passivated 3 entries in 1 milliseconds
 [0m [0m03:50:20,597 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 86) WFLYCLINF0003: Stopped ExternalizerTestCase.war cache from web container
 [0m [0m03:50:20,608 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 86) WFLYCLINF0003: Stopped default-server cache from web container
 [0m [0m03:50:20,617 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment ExternalizerTestCase.war (runtime-name: ExternalizerTestCase.war) in 49ms
 [0m [0m03:50:20,637 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/b9/7ff7d8cfdb2efd79ffe08848debdc7d53d8316/content
 [0m [0m03:50:20,638 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0009: Undeployed "ExternalizerTestCase.war" (runtime-name: "ExternalizerTestCase.war")
 [0m

org.jboss.as.test.clustering.cluster.web.ReplicationForNegotiationAuthenticatorTestCase.testOneRequestSimpleFailover: java.lang.AssertionError: Session failed to replicate after container 1 was shutdown. expected:<2> but was:<1>
	at org.jboss.as.test.clustering.cluster.web.ReplicationForNegotiationAuthenticatorTestCase.testOneRequestSimpleFailover(ReplicationForNegotiationAuthenticatorTestCase.java:114)
------- Stdout: -------
 [0m03:50:20,747 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/1e/e3b2c1892e6876586144e0f8c7c35efddca9dc/content
 [0m [0m03:50:20,749 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "ReplicationForNegotiationAuthenticatorTestCase.war" (runtime-name: "ReplicationForNegotiationAuthenticatorTestCase.war")
 [0m [33m03:50:20,762 WARN  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0080: Valves are no longer supported, org.jboss.security.negotiation.NegotiationAuthenticator is not activated.
 [0m [33m03:50:20,823 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.security.negotiation") which may be changed or removed in future versions without notice.
 [0m [33m03:50:20,824 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m03:50:20,824 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m03:50:20,824 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m03:50:20,824 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m03:50:20,824 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m03:50:20,829 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment ReplicationForNegotiationAuthenticatorTestCase.war
 [0m [0m03:50:20,843 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-7) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ReplicationForNegotiationAuthenticatorTestCase.war"' are as follows:

	java:global/ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	ejb:ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:global/ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean
	java:app/ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean
	java:module/TopologyChangeListenerBean

 [0m [0m03:50:20,934 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 17) WFLYCLINF0002: Started default-server cache from web container
 [0m [33m03:50:20,960 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor is deprecated from CDI 1.1!
 [0m [33m03:50:20,963 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1!
 [0m [0m03:50:20,965 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 20) WFLYCLINF0002: Started ReplicationForNegotiationAuthenticatorTestCase.war cache from web container
 [0m [0m03:50:21,099 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 20) WFLYUT0021: Registered web context: '/ReplicationForNegotiationAuthenticatorTestCase' for server 'default-server'
 [0m [0m03:50:21,133 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "ReplicationForNegotiationAuthenticatorTestCase.war" (runtime-name : "ReplicationForNegotiationAuthenticatorTestCase.war")
 [0m [0m03:50:21,154 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/1e/e3b2c1892e6876586144e0f8c7c35efddca9dc/content
 [0m [0m03:50:21,158 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "ReplicationForNegotiationAuthenticatorTestCase.war" (runtime-name: "ReplicationForNegotiationAuthenticatorTestCase.war")
 [0m [33m03:50:21,176 WARN  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0080: Valves are no longer supported, org.jboss.security.negotiation.NegotiationAuthenticator is not activated.
 [0m [33m03:50:21,208 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.security.negotiation") which may be changed or removed in future versions without notice.
 [0m [33m03:50:21,209 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m03:50:21,209 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m03:50:21,209 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m03:50:21,209 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m03:50:21,209 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m03:50:21,213 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment ReplicationForNegotiationAuthenticatorTestCase.war
 [0m [0m03:50:21,222 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-7) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ReplicationForNegotiationAuthenticatorTestCase.war"' are as follows:

	java:global/ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	ejb:ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:global/ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean
	java:app/ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean
	java:module/TopologyChangeListenerBean

org.jboss.as.test.clustering.cluster.web.ReplicationForNegotiationAuthenticatorTestCase.test: java.lang.AssertionError: expected:<200> but was:<500>
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:69)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:58)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:52)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.establishTopology(AbstractWebFailoverTestCase.java:360)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:120)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:112)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.test(AbstractWebFailoverTestCase.java:103)
------- Stdout: -------
 [0m03:50:22,432 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/0c/3c12c8116d4cd554efc8369e20237d6d351c40/content
 [0m [0m03:50:22,436 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "ReplicationForNegotiationAuthenticatorTestCase.war" (runtime-name: "ReplicationForNegotiationAuthenticatorTestCase.war")
 [0m [33m03:50:22,449 WARN  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0080: Valves are no longer supported, org.jboss.security.negotiation.NegotiationAuthenticator is not activated.
 [0m [33m03:50:22,496 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.security.negotiation") which may be changed or removed in future versions without notice.
 [0m [33m03:50:22,497 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m03:50:22,497 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m03:50:22,497 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m03:50:22,497 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m03:50:22,497 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m03:50:22,502 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment ReplicationForNegotiationAuthenticatorTestCase.war
 [0m [0m03:50:22,525 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ReplicationForNegotiationAuthenticatorTestCase.war"' are as follows:

	java:global/ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	ejb:ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:global/ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean
	java:app/ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean
	java:module/TopologyChangeListenerBean

 [0m [0m03:50:22,631 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 17) WFLYCLINF0002: Started ReplicationForNegotiationAuthenticatorTestCase.war cache from web container
 [0m [33m03:50:22,655 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-1) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor is deprecated from CDI 1.1!
 [0m [33m03:50:22,657 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-1) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1!
 [0m [0m03:50:22,674 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 20) WFLYCLINF0002: Started default-server cache from web container
 [0m [0m03:50:22,816 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 20) WFLYUT0021: Registered web context: '/ReplicationForNegotiationAuthenticatorTestCase' for server 'default-server'
 [0m [0m03:50:22,840 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "ReplicationForNegotiationAuthenticatorTestCase.war" (runtime-name : "ReplicationForNegotiationAuthenticatorTestCase.war")
 [0m [0m03:50:22,866 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/0c/3c12c8116d4cd554efc8369e20237d6d351c40/content
 [0m [0m03:50:22,868 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "ReplicationForNegotiationAuthenticatorTestCase.war" (runtime-name: "ReplicationForNegotiationAuthenticatorTestCase.war")
 [0m [33m03:50:22,886 WARN  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0080: Valves are no longer supported, org.jboss.security.negotiation.NegotiationAuthenticator is not activated.
 [0m [33m03:50:22,919 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.security.negotiation") which may be changed or removed in future versions without notice.
 [0m [33m03:50:22,919 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m03:50:22,919 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m03:50:22,919 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m03:50:22,919 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m03:50:22,919 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.ReplicationForNegotiationAuthenticatorTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m03:50:22,924 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment ReplicationForNegotiationAuthenticatorTestCase.war
 [0m [0m03:50:22,938 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-7) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ReplicationForNegotiationAuthenticatorTestCase.war"' are as follows:

	java:global/ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/ReplicationForNegotiationAuthenticatorTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener

org.jboss.as.test.clustering.cluster.web.ConcurrentFineWebFailoverTestCase.test: java.lang.AssertionError: expected:<200> but was:<500>
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:69)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:58)
	at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:52)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.establishTopology(AbstractWebFailoverTestCase.java:360)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:120)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:112)
	at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.test(AbstractWebFailoverTestCase.java:103)
------- Stdout: -------
 [0m03:48:31,107 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-1/standalone/data/content/05/75ce4b408e06b0eec4d3527d703855073d856b/content
 [0m [0m03:48:31,111 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "ConcurrentFineWebFailoverTestCase.war" (runtime-name: "ConcurrentFineWebFailoverTestCase.war")
 [0m [33m03:48:31,253 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m03:48:31,253 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m03:48:31,253 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m03:48:31,253 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m03:48:31,253 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m03:48:31,280 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment ConcurrentFineWebFailoverTestCase.war
 [0m [0m03:48:31,334 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.3.6.Final
 [0m [0m03:48:31,408 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ConcurrentFineWebFailoverTestCase.war"' are as follows:

	java:global/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	ejb:ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:global/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean
	java:app/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean
	java:module/TopologyChangeListenerBean

 [0m [0m03:48:31,652 INFO  [org.jboss.weld.Version] (MSC service thread 1-6) WELD-000900: 3.0.4 (Final)
 [0m [0m03:48:31,851 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 12) WFLYCLINF0002: Started default-server cache from web container
 [0m [0m03:48:31,885 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 3) WFLYCLINF0002: Started ConcurrentFineWebFailoverTestCase.war cache from web container
 [0m [33m03:48:32,090 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor is deprecated from CDI 1.1!
 [0m [33m03:48:32,103 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-3) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1!
 [0m [0m03:48:32,686 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 12) WFLYUT0021: Registered web context: '/ConcurrentFineWebFailoverTestCase' for server 'default-server'
 [0m [0m03:48:32,718 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "ConcurrentFineWebFailoverTestCase.war" (runtime-name : "ConcurrentFineWebFailoverTestCase.war")
 [0m [0m03:48:32,812 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /store/work/tc-work/37b47ae8b9c60325/full/testsuite/integration/clustering/target/wildfly-2/standalone/data/content/93/dbcf142e9fe403cbae607d653e9d9e69bed4f8/content
 [0m [0m03:48:32,815 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "ConcurrentFineWebFailoverTestCase.war" (runtime-name: "ConcurrentFineWebFailoverTestCase.war")
 [0m [33m03:48:32,906 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.clustering.common") which may be changed or removed in future versions without notice.
 [0m [33m03:48:32,906 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.controller") which may be changed or removed in future versions without notice.
 [0m [33m03:48:32,906 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.jboss.as.server") which may be changed or removed in future versions without notice.
 [0m [33m03:48:32,906 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.infinispan") which may be changed or removed in future versions without notice.
 [0m [33m03:48:32,906 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.ConcurrentFineWebFailoverTestCase.war" is using a private module ("org.wildfly.clustering.infinispan.spi") which may be changed or removed in future versions without notice.
 [0m [0m03:48:32,946 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment ConcurrentFineWebFailoverTestCase.war
 [0m [0m03:48:33,004 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.3.6.Final
 [0m [0m03:48:33,074 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'TopologyChangeListenerBean' in deployment unit 'deployment "ConcurrentFineWebFailoverTestCase.war"' are as follows:

	java:global/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:app/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:module/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener
	java:jboss/exported/ConcurrentFineWebFailoverTestCase/TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener

@yersan AFAIK removal of the solaris machine was done just as a temporary solution due to lack of building machines available. Solaris support should be put back to EAP7.2, see https://issues.jboss.org/browse/JBEAP-14596. We should assure this bit is not forgotten when moving back this support.


How to restore the Database in a different region, if the origin backup region is unavailable

I wonder if and how you can restore a Database to a different Region?
In Case the VM Service in a Region is unavailble, you wouldn't be able to restore the Backup of a Database at all, right?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 89e13d87-ad6b-accc-6cbd-de6fad4435d4
Version Independent ID: 654c5cec-2946-87fa-8b33-a82ffd4f3758
Content: Restore SQL Server databases on an Azure VM - Azure Backup
Content Source: articles/backup/restore-sql-database-azure-vm.md
Service: backup
GitHub Login: @dcurwin
Microsoft Alias: dacurwin

@jhueppauff  Thanks for your comment. We are actively investigating and will get back to you shortly.

#reassign:sachdevaswati

Hello,
I am assuming the question is regarding Restoring to a 'paired' secondary region and not just any region. This capability is called Cross Region Restore (CRR) in case of IaaS VM backup. We will roll out this capability for SQL VM backup in Jul-Aug timeframe.
Please note, although we do have geo-redundancy (GRS) setting for the backups, but those are not retrievable till the time Azure declares an outage and this happens very rarely. CRR will overcome this limitation.

The answer above should answer your question, so we will now close this issue. If this remains an issue, please reply and we will gladly continue the discussion.
#please-close


Slow Startup When Inside Region; Conflicting Events

Thanks for the excellent library! We're trying to use it as part of an app for CS 125 @ Illinois to track when our course staff (and eventually students) come and go into a room that we use for office hours. Source code is here: https://github.com/gchallen/cs125_app. I'm very new to flutter and to Dart so am just trying to get something simple working that logs when regions are entered and exited from.
I'm having two problems at present. First, the library seems slow to report when the app is restarted inside an existing region. This is in contrast to the fairly quick reports that are generated when regions are exited or entered, or when I turn the beacon on and off—those appear within a few seconds. When I do a restart of the app with an existing beacon nearby, several minutes go by before the first reports are received. However, the library does seem to know it's inside an existing region based on this message from the logs:
06-21 09:18:38.711 20541-20541/edu.illinois.cs.cs125.cs125app I/ScanJob: We are inside a beacon region.  We will not scan between cycles.

So is there a way to query on startup to determine the current region? I didn't see that in the API description, although not everything seems to be documented yet.
Second, the beacon does begin to be reported I'm getting repeated pairs of exited region + entered region messages back to back. That doesn't seem to happen in other scenarios: for example, when I turn the beacon on and off I get one message back, not a pair. Obviously we could do some debouncing in our app but I thought perhaps this was related to the issue I described above.

Hello, are you testing on iOS or Android?
Can you reproduce the issue on both platforms?
Under the hood implementations are very different and the issue might be specific to one platform. That would help a lot for debugging.

Testing on Android. I don't have an iOS device to test with at this point, and the emulator isn't helpful here... sorry.
Easiest steps to reproduce:
.  Receive notifications promptly.
. Close app.
. Restart app... and wait.
. Eventually you begin to see pairs of exited/entered at regular but slow intervals.

Ok will try to tomorrow on iOS & android, see if I can reproduce.
In the meantime would you mind trying and report back behaviour using the following android app: https://github.com/AltBeacon/android-beacon-library-reference
It's the library that the plugin is using for working with beacons on android.

So I've noticed this now on a React Native library that also uses AltBeacon. You might want to peek at the writeup here: https://github.com/MacKentoch/react-native-beacons-manager/issues/99.
Essentially it seems that AltBeacon > 2.8 stopped delivering didEnterRegion events when the app is restarted. There is a different event that you are supposed to use called didDetermineStateForRegion: https://altbeacon.github.io/android-beacon-library/state-persistence.html.
Would it be possible for this library to forward that event? It looks like there is just a log message there currently.

Thanks for the research! I will implement a fix tomorrow.

Great, thanks! However, note that I'm not sure that this will fix the underlying issue. I've opened this bug against AltBeacon itself, since I was able to reproduce the behavior using their reference app.
Perhaps this is the result of the cheap iBeacons I'm using. Any advice on good low-cost alternatives?

Unfortunately I have no idea, I have very little experience with beacons outside of our test lab.
This library was developed for and sponsored by Pointz.
Maybe @AndrewPetrovics knows some good and reliable hardware?
I will track closely https://github.com/AltBeacon/android-beacon-library/issues/708.

@gchallen can you try to update the reference project of android-beacon-library by adding beaconManager.setRegionStatePersistenceEnabled(false) as suggested in https://github.com/AltBeacon/android-beacon-library/issues/708?
If it works, it seems to me that the clean way of handling this would be by exposing this option on the flutter side.
Beacons.configure(BeaconsSettings(android: BeaconsSettingsAndroid(regionStatePersistenceEnabled: false)));

Let me know. Thanks.

@gchallen Were you able to make more experimentation with android-beacon-library?
Right now I'm thinking about allowing more options on setup method in order to customize the working of android-beacon-library, but leaving the default behaviour consistent with the original library.

Sorry for the delay—I've been out of town without access to a testing harness. IIRC I did try this and it does work properly, although it doesn't debounce the spurious enter and exit events.
FYI I've moved both away from Flutter and away from general beacons for this project (in favor of Estimotes), so future testing may be limited. But overall your solution sounds like a good one.

I would like to fork this and test it on my own. although I have to configure my own beacons than you are using. I am using Sensoro Smart4aa... I have a hard time reading how to set up the instructions provided in the README.md. I will try to continue with your project btw. Thanks!


Upgrade to netcoreapp2.2 and remove netcoreapp2.0 testing

cc @ryanbrandenburg

Oh, NM, SignalR wasn't part of my script because it didn't exist the last time I did this.

Fix the commit title

I fixed it for you...


Fix panic on mcapp install

Address issue: https://github.com/rancher/rancher/issues/18670
Problem:
Panic happens on mcapp install when talking to a 2C4G single node K8S with Rancher HA installed and a GKE cluster provisioned. It does not happen in a standalone rancher.
Inspecting the code, it is probably because the heavy loaded Rancher/K8S takes longer time to handle the conditions thus we get nil status when fetching the mcapp object after it is created.

I don't think it is a good way to fix it but we can still have this PR for workaround. I would like to have a comment for why you are doing this in the code and we can fix it later.

The mcapp.status is initialized with nil, so we should do the check anyway. The panic does not happen when the controller updates status before the client gets the mcapp object.
Added a comment for explanation.

LGTM


Exception SASL SCRAM User when password is vaulted

Describe the issue
Using your playbook with sasl_protocol to scram. If you set user password vaulted, you have an exception in this task :
fatal: [XXXXXXX]: FAILED! => {"msg": "An unhandled exception occurred while templating '{{ kafka_broker_combined_properties | combine(kafka_broker_custom_properties) }}'. [....] can only concatenate str (not "AnsibleVaultEncryptedUnicode") to str"}
I think problem raise from combine_properties function because in default configuration password is string. So if password is vault encode myabe fix it with 'toString() python method' :

    def combine_properties(self, properties_dict):
        # Loops over master properties dictionary and combines sub elements if enabled
        final_dict = {}
        for prop in properties_dict:
            if properties_dict[prop].get('enabled'):
                final_dict.update(properties_dict[prop].get('properties'))
        return final_dict

To Reproduce
All Vars Configuration :
    sasl_protocol: scram

    sasl_scram_users:
      admin:
        principal: "admin"
        password: !vault |
          $ANSIBLE_VAULT;1.1;AES256
<PHONE_NUMBER>6131333038303532613231653233343565303831396530393061643031303432303632
<PHONE_NUMBER>393563343861643834336430353930643062370a663563376131653664653430363963
<PHONE_NUMBER>3937646635663032326266383439623736623462373632313934643261303634663732
<PHONE_NUMBER>623337610a616365613231346630656564616265656231633238313932333437363461
<PHONE_NUMBER>6531656463353562323165376135653631316435653337366164653063
      client:
        principal: "client"
        password: !vault |
          $ANSIBLE_VAULT;1.1;AES256
<PHONE_NUMBER>3833386164616630353966363231633234633561663464653931393835653830303630
<PHONE_NUMBER>396137653637383332656539373766346438370a353164383737306535646234363065
<PHONE_NUMBER>3439663064346564333062373265653036646137306531353336323931653931363032
<PHONE_NUMBER>366531640a323161386538333966646635353462623263346234306631383635646237
<PHONE_NUMBER>3736346362616562623061333438613461616162386532373266393166

Workaround
A workaround exist, you need to convert vault encoded string :
    sasl_protocol: scram

    sasl_admin_password: !vault |
      $ANSIBLE_VAULT;1.1;AES256
<PHONE_NUMBER>6131333038303532613231653233343565303831396530393061643031303432303632
<PHONE_NUMBER>393563343861643834336430353930643062370a663563376131653664653430363963
<PHONE_NUMBER>3937646635663032326266383439623736623462373632313934643261303634663732
<PHONE_NUMBER>623337610a616365613231346630656564616265656231633238313932333437363461
<PHONE_NUMBER>6531656463353562323165376135653631316435653337366164653063

    sasl_client_password: !vault |
      $ANSIBLE_VAULT;1.1;AES256
<PHONE_NUMBER>3833386164616630353966363231633234633561663464653931393835653830303630
<PHONE_NUMBER>396137653637383332656539373766346438370a353164383737306535646234363065
<PHONE_NUMBER>3439663064346564333062373265653036646137306531353336323931653931363032
<PHONE_NUMBER>366531640a323161386538333966646635353462623263346234306631383635646237
<PHONE_NUMBER>3736346362616562623061333438613461616162386532373266393166

    sasl_scram_users:
      admin:
        principal: "admin"
        password: "{{sasl_admin_password|string}}"
      client:
        principal: "client"
        password: "{{sasl_client_password|string}}"

@LGouellec Could the following Ansible best practice be a valid workaround for you: https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html#keep-vaulted-variables-safely-visible, or is that irrelevant for the issue?

Hi @erikgb,
Yeah it's a valid workaround.
Could we not manage AnsibleVaultEncryptedUnicode in the function combine_properties ?

Yeah it's a valid workaround.

That's nice! 👍

Could we not manage AnsibleVaultEncryptedUnicode in the function combine_properties ?

Yes, I think this could be fixed. Please submit a PR to fix this, and we can review it. This bug will be put in our backlog and handled according to best effort as described here. Or use Confluent Support if you are a Confluent customer.

Resolved in PR #640


[Feature Request] System Shortcut Bypass

So I tries to create a pie menu for the windows key but then I realized that all my windows shortcuts are now useless unless i recreate a submenu for all the shortcuts that I use with the windows key.
And so it would be very helpful if we could use our shortcut combinations,
So the algorithm would be like this:

win button pressed and held
pie menu appears
other combination key pressed
pie menu disappears and shortcut is executed

This makes sense to me being that it's such an accessible key.  I'll see if this can be done.  In the meantime, capslock and tilde are also decent keys to sacrifice.

This could also be solved with a different activation mode, let's call it 'On Move', where the menu only opens when the mouse moves a set number of pixels while the key's held, and if the key is released without this being the case, the original hotkey is executed.
I use this all the time in Blender with Pie Menu Editor, so I can re-use existing hotkeys! I want to use it here to create an alternative to the right mouse context menu in Firefox, without taking away access to the original


Report error if class uses extended type before its declaration

Fixes #4341

I am still working on reporting error if alias is declared before it is referencing entity(internal alias only)

This PR is superseded by #8636 which has been successfully merged, right?

closing in favor of https://github.com/Microsoft/TypeScript/pull/8636


Fix Commands null tolerance test

The causes of the failure were following:

Not checking the test result (NullToletranceTest does not fail the test but returns a boolean value).
Commands class could not pass the tests by their design.
After one failed method checked false was returned. The methods order is undefined though, that's why we could not reproduce the problem in our local environments.
Not setting default values for the custom parameter types caused an error when trying to get one.

What's done:

Check the test result.
Fit Commands to our requirements.
Add an error message for the missing default value case.

Also, I've turned off the checks for synthetic methods (Smth#access$000), since we declare to check non-private methods only.

@alexander-yevsyukov PTAL

@alexander-yevsyukov PTAL again


add offloadSegmentUnafe to allow separate threads to manage segment offloading

Add offloadSegmentUnafe which offload segments w/o taking the segment locks internally, to allow separate threads to offload segment w/o subject to potential deadlocks on segmentLocks

Codecov Report
Attention: Patch coverage is 0% with 13 lines in your changes missing coverage. Please review.

Project coverage is 0.00%. Comparing base (59551e4) to head (1eefcb5).
Report is 699 commits behind head on master.

Files
Patch %
Lines

.../pinot/core/data/manager/BaseTableDataManager.java
0.00%
11 Missing :warning:

...cal/upsert/BasePartitionUpsertMetadataManager.java
0.00%
2 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (1eefcb5). Click for more details.
HEAD has 48 uploads less than BASE

Flag
BASE (59551e4)
HEAD (1eefcb5)

integration
7
2

integration2
3
2

temurin
12
2

java-21
7
2

skip-bytebuffers-true
3
1

skip-bytebuffers-false
7
1

unittests
5
0

unittests1
2
0

java-11
5
0

unittests2
3
0

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #13517       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436     2484       +48
  Lines        133233   137713     +4480
  Branches      20636    21381      +745
=============================================
- Hits          82274        0    -82274
- Misses        44911   137713    +92802
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <0.00%> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <0.00%> (ø)

java-11
?

java-21
0.00% <0.00%> (-61.63%)
:arrow_down:

skip-bytebuffers-false
0.00% <0.00%> (-61.75%)
:arrow_down:

skip-bytebuffers-true
0.00% <0.00%> (-27.73%)
:arrow_down:

temurin
0.00% <0.00%> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


fix: simplifying destructing syntax to avoid vite optimisation issue

Following https://github.com/storybookjs/addon-svelte-csf/pull/181. We faced an issue (probably related to vite optimisation) as explained by @xeho91 in https://github.com/storybookjs/addon-svelte-csf/pull/181#issuecomment-2211041666
The problem was linked to the destructuring assignment syntax in the src/runtime/Story.svelte file with the props of the componet.
This PR remove the destructuring assignment in favour of a single variable, this fixing all compilation issue.

I'm not sure if this the right solution to the problem.
AFAIK, $props rune return value object properties are [meant to be destructed]https://svelte-5-preview.vercel.app/docs/runes#$props)
I do remember about your issue, and yet I haven't been able to reproduce it on other projects than yours. I need to consider the possibility that maybe the cause of this issue lies somewhere else - the error message and the error stack trace could be misleading. I'll try to investigate again with vite-plugin-inspect tonight my time.

@axel7083
I've got a possible lead.
I can't verify right now with podman-desktop repository, but if you could find a time...
I believe the error could be connected with svelte-preprocess.
Does the error still occur if you temporarily disable it inside svelte.config.js?
If yes, that'll be good news. Because that'll help us narrow the scope of where the issue occurs. And it might be easier to provide reproduction for Svelte maintainers.

I believe the error could be connected with svelte-preprocess. Does the error still occur if you temporarily disable it inside svelte.config.js?

@xeho91 deleting the svelte.config.js file fixes the compilation issue, the problem seems to be linked to the svelte-preprocess library then. Thanks for narrowing down the problem

Does this mean that we can close this, or is there still an actual issue hidden somewhere in the addon?

Does this mean that we can close this, or is there still an actual issue hidden somewhere in the addon?

Yes, AFAIK the issue is related to vite configuration conflict between vite-preprocess, and @sveltejs/vite-plugin-svelte.
I we can't do anything on our side, nor I have idea how to resolve or provide a simple reproduction.
If it occurs again to someone else, and can provide a simple reproduction, then you'll have a better luck reporting it either to:

https://github.com/sveltejs/vite-plugin-svelte
or https://github.com/sveltejs/svelte-preprocess

In the light of how much I learned and know so far, I'm not sure which one is at fault.
Both repositories belong to same organisation, so they will be able to transfer issue in case. But first, a simple reproduction.


Markdown referenced file can not be displayer

Is your feature request related to a problem? Please describe.
For exaple , in the examle.md, I added
![name](name.md)

In obsidian, the content of name.md is displaced inside example.md.
But in generarted HTML, they are disapeared.

Is your feature request related to a problem? Please describe.
For exaple , in the examle.md, I added
![name](name.md)

In obsidian, the content of name.md is displaced inside example.md.
But in generarted HTML, they are disapeared.

https://github.com/KosmosisDire/obsidian-webpage-export/issues/207
I feel like it's the same problem。

Yes this is a duplicate so I will close it. This issue will be fixed in the next update


Meeting 8 Notes

Wiki page for Meeting 8 has been created and added to sidebar. You can check the page here.


Peptides train/valid/test split

Is this PR still relevant? I think it should not be used in its current form.


GEODE-6964: Move geode log4j-core classes to geode-log4j

Make geode-log4j an implementation dependency for geode-dunit.
Co-authored-by: Mark Hanson<EMAIL_ADDRESS>

@kirklund It looks like this new module will export two root packages, o.a.g.alerting and o.a.g.logging. As we move towards Java 9 modules we need to make sure that jars have unique package exports. Can you verify that geode-core will no longer exports these two packages? Would it make sense to move o.a.g.alerting to o.a.g.loggging.alerting so that this module only exports a single root package? See geode-cqgradle for adding module information to the jar.
Also if the use of log4j is an implementation detail, and the root package is o.a.g.logging, then perhaps this module should be 'geode-loggingand notgeode-log4j`?

@pivotal-jbarrett The name geode-log4j is meant to describe this as the log4j-core implementation of Geode Logging as opposed to the yet-to-be-created geode-logback which would be the logback implementation of Geode Logging. The idea is that if you want to use log4j-core with Geode then drop this jar in your classpath. The pom dependency is implementation because these classes don't provide user APIs that return log4j-core classes, they simply install an SPI provider that enables Geode log-level, log-file, etc to interact with log4j-core. Without these provider classes, the logging properties and logging GFSH commands do nothing.
This module will export org.apache.geode.logging.log4j. geode-core will export org.apache.geode.logging and org.apache.geode.logging.spi. (I have a few changes I still need to make).
I can move the Alerting classes from alerting packages into logging packages. I was originally intending to keep them separate even though both are implemented with log4j-core -- and could thus be implemented in geode-logback with logback instead.

@kirklund this sounds very cool!

Closing this PR in favor of https://github.com/apache/geode/pull/3914


bash prompt broken for long lines

if you type a line that wraps, the cursor gets out of sync

[ ] were supposed to fix this, but they showed up in the prompt verbatim. Maybe needs different escaping. E.g. maybe try a $'' string


Transparent images have black background

Thank you for maintaining vimage!
Some time in the last few months transparent images stopped appearing transparent. I've tried reverting to previous versions of vimage, but they all have this problem.

Weird. Transparency still works fine for me.
Does turning transparency on/off do anything? What about changing the different background colour in the settings?
Have you tried updating Windows and/or your graphics drivers?


TODO:  Create a "live" GSoC 2022 section

Create menu hierachy to support our GSoC and GSoD Communities:
Community
    Google Summer of Code 2022
         Program information   --->  https://docs.rocket.chat/contributors/google-summer-of-code/google-summer-of-code-2021
         Introductions  --->  https://open.rocket.chat/channel/gsoc2022
         Team -->  https://open.rocket.chat/channel/google-summer-of-code
         Leaderboard ->  https://gsoc.rocket.chat
         Virtual Conference -> https://rocket.chat
         Office Hours ->  https://rocket.chat
         Projects Ideas ->  https://docs.rocket.chat/contributors/google-summer-of-code/google-summer-of-code-2021#project-ideas
         Results -> https://docs.rocket.chat/contributors/google-summer-of-code/google-summer-of-code-2021#update-may-20th-2021
    Google Season of Doc 2022
       Program information   --->  https://docs.rocket.chat/contributors/google-season-of-docs/google-season-of-docs-2021
       Introductions  --->  https://open.rocket.chat/channel/gsod2022

I'm working on this one

Hello, is this issue still open, if yes then I would love to work on it

@Sing-Li if this issue is still open I would like to work on it.


feat!: add attestation source library and re-work policy logic

This is a fairly major re-work of how we handle finding attestations in
the policy engine. Now the policy engine expects a VerifiedSource that
will query another source to find relevant attestations for each policy
step.
Rekor support is removed.
Archivist support is added.

Still working on fixing existing and adding additional test cases for these functionalities so this is still a draft.
Ready for architectural and technical review.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

63 of 85 (74.12%)  changed or added relevant lines in 3 files are covered.
17 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-1.3%) to 42.413%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

policy/errors.go
0
3
0.0%

policy/policy.go
59
78
75.64%

Files with Coverage Reduction
New Missed Lines
%

policy/step.go
6
60.42%

policy/policy.go
11
50.82%

Totals

Change from base Build<PHONE_NUMBER>:
-1.3%

Covered Lines:
805

Relevant Lines:
1898

💛  - Coveralls

This seems to have been working fine in current use. Gonna go ahead and merge it so it doesn't sit too long


WIP: Integration with tsd-jsdoc for generating typings

References #5717
This PR contains modifications in the jsdoc block tags so that we can nicely integrate with tsd-jsdoc and create a typings file for the library. Initially we are adding missing jsdoc block tags in order for tsd-jsdoc to have a first time pass from each subfolder of Sources directory and compile successfully.

[x]  Core
[x]  Renderer
[ ]  Scene

Thanks for the pull request @bampakoa!  These changes look good so far.  Let us know when this is ready for a full review

@hpinkos I have added the namespace block in AutomaticUniforms file as stated in Using @alias for an object literal. I am not really sure if namespace should be added, but something was missing there and I think namespace is a good fit. What do you think?

@hpinkos I have noticed that Cesium uses internalConstructor block tag in various pieces of the code, which is not part of the standard JSDoc syntax? What is this all about?

@bampakoa this is one of our custom tags.  You can see the others here: https://github.com/AnalyticalGraphicsInc/cesium/blob/master/Tools/jsdoc/cesiumTags.js
internalConstructor is an alias of class.  We use it to denote things that shouldn't be instantiated by the end user.  For example Billboard has a constructor, but you should never call new Billboard().  Instead, you create one using billboardCollection.add({ billboardProperties }).

@hpinkos I added also class block tag where internalConstructor is used so that jsdoc can understand the actual tag.

I just had that one comment.  These changes look fine to me.  Does anyone else want to take a look?  I'll merge this by the end of the week if no one else has comments

@hpinkos the changes in the PR are available for review

Everything looks good @bampakoa! I can confirm the documentation builds correctly.

I'll add a comment to CHANGES.md in master

I would have done it, as @cesium-concierge notified me about it, but I thought it was not meant to be an actual change 🤔

No worries 😄 I just decided to do it to save some additional back and forth.  I wasn't sure if it warranted a line in CHANGES initially, but I think other users using TypeScript will be interested in this so I decided to add it.  Thanks again for the contribution!


Q2/2022 Roadmap

This PR adds the initial thoughts about the Q2 roadmap.

And don't forget to put @alallema as reviewer, especially because she was not there during the meeting :)


error :  failed: Malformed IDX file

Gitea version 1.13.4
Git version: 2.7.4 ( built gitea myself)
Operating system: ubuntu/xenial
Database (use [x]):

[ ] PostgreSQL
[x ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x ] No

Log gist: ~/gitea/log/gitea.log

Description
I have this error when I start gitea:
2021/03/15 09:05:58 ...dexer/stats/queue.go:24:handle() [E] stats queue indexer.Index(409) failed: no such file or directory
2021/03/15 09:05:59 ...dexer/stats/queue.go:24:handle() [E] stats queue indexer.Index(11) failed: Malformed IDX file

Here is my systemd launcher
[Unit]
Description=Gitea (Git with a cup of tea)
After=syslog.target
After=network.target
#After=mysqld.service
#After=postgresql.service
#After=memcached.service
#After=redis.service

[Service]
# Modify these two values and uncomment them if you have
# repos with lots of files and get an HTTP error 500 because
# of that
###
LimitMEMLOCK=infinity
LimitNOFILE=65535
RestartSec=2s
Type=simple
User=git
Group=git
WorkingDirectory=/home/git/gitea
ExecStart=/home/git/gitea/gitea web
Restart=always
Environment=USER=git HOME=/home/git

[Install]
WantedBy=multi-user.target

This happens due to Gitea not being stopped cleanly. You can remedy this by removing the queue files, or by switching to a different non-file based queue. Please hop into our chat and we'd be happy to guide you through that process :)

So actually this problem is a different problem.
The error is coming from go-git trying to open the repository and it is reporting a malformed IDX file - I'm not entirely certain why this is the case - but it shouldn't be a problem on 1.14 as we don't use go-git by default there anymore.
Likely the issue is that the repository doesn't exist but I'm not certain.


DRAFT: Do not merge

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

Is the change a dependency upgrade?

How was this patch tested?

looks like HIVE-27273 broke the semijoin filter


[Button] Add loading prop support

      <Button variant="outlined" loading>
        Loading…
      </Button>
      <Button
        variant="contained"
        color="primary"
        loading
        startIcon={<CircularProgress color="inherit" size={16} />}
      >
        Duplicate
      </Button>

Benchmark
The implementation was benchmarked with the following sources. I have noticed that the loading and disabled states are often styled independently.

evergreen

blueprint

vuetify

cosmos

antd

element

sancho

semantic ui

quasar

baseui

atlaskit

chakra

orbit

I'm closing, it doesn't seem to be a very frequent use request but it seems to require more effort to reach a consensu at least, we have https://material-ui.com/components/progress/#interactive-integration.

more effort to reach a consensus

Well, actually, BusyButton might be a good enough solution.


CRUD bucket feature for Azure and GCP

This PR is to support bucket creation in Azure and GCP clouds from soda. Earlier a soda user need to manually create and delete bucket in various clouds. But now they can create and delete bucket from soda clients.
Request to create bucket in azure:

Bucket created in SODA:

Bucket created in azure cloud:

Request to create bucket in GCP:

Bucket created in SODA:

Bucket created in GCP cloud:

LGTM


staticpod/startupmonitor: add fallback support to installer controller

This implements the operator-side exponential backoff retry (10min to 2h, 1.5 factor) after fallback, described in https://github.com/openshift/enhancements/pull/833.

/hold
until proof PR is green.

/hold cancel

/lgtm


feat(ios): allow enabling fullscreen functions

With this change, developers can enable the fullscreen API in their apps. This can be useful for example to make iframes fullscreen.
Related issue: https://github.com/ionic-team/cordova-plugin-ionic-webview/issues/350

@jcesarmobile It's possible to merge this?


update url in git clone instructions

so people can clone it easily

@pywebdesign circleci didn't seem to be set up correctly when you created the PR, can you trigger an update on the branch so CI can kick off?


Main page and sign up form impl

@jdville03 issue resolved! Thanks for the heads up

Thanks for the fixes and getting the preview up! I'll pass along a few comments today. Nothing major but see a few broken links and want to take a closer run through it all.

@sophiacodes in the interest of time and to be able to validate my changes live, I made some updates in the form of a new PR #101 to merge into this one. Hope you don't mind and let me know if you have any questions on it.

Merge overridden on request, GH seems to have been improperly blocked waiting for deploy status.


Migrate log4j-jdbc-dbcp2 to JUnit 5

Hello! 👋
We are from Neighbourhoodie, the implementation partner of the STF Bug Resilience Program. This work is part of our agreed Milestone 1. Upgrade from JUnit 4 to JUnit 5. This PR migrates the tests located in log4j-jdbc-dbcp2 to JUnit5.

Our idea is to deliver small size PRs with the changes. If you'd like us to do it in some other way, please tell us so
Part of the deliverable is to transport these changes from the 2.x branch to the main branch. Should we create the PR against main once this PR is merged?

Thank you!

Original PR on their side https://github.com/apache/logging-log4j2/pull/3007 was merged