[JBoss JIRA] (SWSQE-1077) Kiali Test For Istio.io
by Hayk Hovsepyan (Jira)
[ https://issues.redhat.com/browse/SWSQE-1077?page=com.atlassian.jira.plugi... ]
Hayk Hovsepyan updated SWSQE-1077:
----------------------------------
Sprint: Kiali Sprint #32, Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44, Kiali Sprint #45, Kiali Sprint #46, Kiali Sprint #47 (was: Kiali Sprint #32, Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44, Kiali Sprint #45, Kiali Sprint #46)
> Kiali Test For Istio.io
> -----------------------
>
> Key: SWSQE-1077
> URL: https://issues.redhat.com/browse/SWSQE-1077
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Matthew Mahoney
> Priority: Major
> Labels: infrastructure
>
> The Istio.io team is requesting a Kiali test case that can be run on each submitted PR. The purpose of this test case is to validate that Kiali is not broken upon a PR submittal.
> Meeting with [~brian.avery] [~gbaufake]:
> 1) BrianA to port existing Kiali test case that was developed in old Istio.io test framework to new istiso.io framework
> https://github.com/istio/istio/blob/master/tests/e2e/tests/kiali/kiali_te...
> 2) Kiali team then to add an api test case(s) via 'curl' to validate the Istio/Kiali integration is properly functioning.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (SWSQE-1089) Remove hardcoded waiting for webhook "smcp.validation.maistra.io"
by Hayk Hovsepyan (Jira)
[ https://issues.redhat.com/browse/SWSQE-1089?page=com.atlassian.jira.plugi... ]
Hayk Hovsepyan updated SWSQE-1089:
----------------------------------
Sprint: Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44, Kiali Sprint #45, Kiali Sprint #46, Kiali Sprint #47 (was: Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44, Kiali Sprint #45, Kiali Sprint #46)
> Remove hardcoded waiting for webhook "smcp.validation.maistra.io"
> -----------------------------------------------------------------
>
> Key: SWSQE-1089
> URL: https://issues.redhat.com/browse/SWSQE-1089
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Filip Brychta
> Assignee: Filip Brychta
> Priority: Optional
> Labels: infrastructure
>
> https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-jenkins-dsl/blob/ma...
> There is no need to wait that long. We need some dynamic check.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (SWSQE-1182) DropDown - Optimization of hierarchy.
by Hayk Hovsepyan (Jira)
[ https://issues.redhat.com/browse/SWSQE-1182?page=com.atlassian.jira.plugi... ]
Hayk Hovsepyan updated SWSQE-1182:
----------------------------------
Sprint: Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44, Kiali Sprint #45, Kiali Sprint #46, Kiali Sprint #47 (was: Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44, Kiali Sprint #45, Kiali Sprint #46)
> DropDown - Optimization of hierarchy.
> -------------------------------------
>
> Key: SWSQE-1182
> URL: https://issues.redhat.com/browse/SWSQE-1182
> Project: Kiali QE
> Issue Type: Task
> Reporter: Hayk Hovsepyan
> Assignee: Hayk Hovsepyan
> Priority: Major
> Labels: automation
>
> Currently there is a big hierarchy of DropDown objects.
> It needs to be optimized.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (JGRP-2418) Impedence mismatch between message types and transports
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2418?page=com.atlassian.jira.plugin... ]
Bela Ban commented on JGRP-2418:
--------------------------------
Hmm, there is a problem: we cannot only send the ByteBuffer passed to us, but we also need to generate some metadata (version, headers, src and dest address), which prepends the buffer.
This is memory allocation, so it is not better than the temp buffer which exists today to write the ByteBuffer to the output stream. In addition, we'd need to change the signature of {{send(ByteBuffer)}} to {{send(ByteBuffer[])}} in BaseServer, in order to be able to pass _multiple_ ByteBuffers to BaseServer.
I'll investigate a bit more, but atm, there seems to be no gain to be had. On the contrary, some bundlers (RingBufferBundler) would have to create temp lists to be able to pass messages to the same destinations to the transport, rather than writing directly to the output stream.
> Impedence mismatch between message types and transports
> -------------------------------------------------------
>
> Key: JGRP-2418
> URL: https://issues.redhat.com/browse/JGRP-2418
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 5.1
>
>
> When sending a message (_of any type_), it is currently marshalled into a byte[] array, which is handled differently by each transport:
> * UDP wraps it into a DatagramPacket and calls DatagramSocket.send()
> * TCP writes the array to the socket's output stream
> * TCP_NIO2 wraps it into a {{ByteBuffer}} and calls SocketChannel.write(ByteBuffer)
> In some cases, there is an impedance mismatch between the type of the message and the type of the transport: for example, when sending an NioMessage (containing a ByteBuffer), we don't actually need the conversion to byte array and the subsequent wrapping into a ByteBuffer; this is superfluous. Even worse, when using off-heap, this creates an unneeded memory allocation. Passing the *same* ByteBuffer all the way down from the application to the transport would be better.
> This requires changes in the way bundlers accumulate messages. Also, perhaps the transport itself should become an SPI, to which a generic {{Transport}} protocol delegates. This would also allow us to implement multiple transports (JGRP-1424) in the same stack.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (DROOLS-5577) Calling static Java method from DMN model (Drools Business Central)
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-5577?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-5577:
-----------------------------------
Workaround Description:
# Ignore this validation error (red popup) while Saving the DMN Model with the editor
# Proceed to Deploy the KJAR BC Project as usual
Workaround: Workaround Exists
> Calling static Java method from DMN model (Drools Business Central)
> -------------------------------------------------------------------
>
> Key: DROOLS-5577
> URL: https://issues.redhat.com/browse/DROOLS-5577
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor, dmn engine
> Affects Versions: 7.40.0.Final
> Reporter: Kristina Mandekic
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: support
> Attachments: Artifacts.PNG, Artifacts0.PNG, DroolsNewTypes5-0.0.1-SNAPSHOT.jar, dependencies.PNG, stdev 0.PNG, stdev 1.PNG
>
>
> When calling static Java method {{stdev_a}} (which I created in a new Java Maven project) from Drools Business Central DMN project/model, I'm getting following error:
>
> {code:java}
> DMN: Error compiling Java function 'stdev' on node 'stdev': Error resolving external function as defined by: function(val) external { java: { class: ""com.samplea.drools.DroolsNewTypes5.StandardDeviationA"", method signature: ""stdev_a(java.lang.Number)"" }} (DMN id: _3B4B6CBE-847B-4488-8754-214F506BBB48, Error compiling the referenced FEEL expression){code}
>
> Also, how to view logs of DMN model when it has build errors?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (DROOLS-4768) org.drools.compiler.integrationtests.CompositeAgendaTest.testCreateHaltDisposeAgenda timeouts
by Marek Novotny (Jira)
[ https://issues.redhat.com/browse/DROOLS-4768?page=com.atlassian.jira.plug... ]
Marek Novotny updated DROOLS-4768:
----------------------------------
Labels: tests-failures (was: )
> org.drools.compiler.integrationtests.CompositeAgendaTest.testCreateHaltDisposeAgenda timeouts
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-4768
> URL: https://issues.redhat.com/browse/DROOLS-4768
> Project: Drools
> Issue Type: Bug
> Reporter: Marek Novotny
> Assignee: Daniel Rosa
> Priority: Major
> Labels: tests-failures
> Fix For: 7.31.0.Final
>
>
> {{noformat}}
> org.junit.runners.model.TestTimedOutException: test timed out after 40000 milliseconds
> at java.util.zip.ZipFile.freeEntry(Native Method)
> at java.util.zip.ZipFile.access$1000(ZipFile.java:60)
> at java.util.zip.ZipFile$ZipEntryIterator.next(ZipFile.java:540)
> at java.util.zip.ZipFile$ZipEntryIterator.nextElement(ZipFile.java:514)
> at java.util.zip.ZipFile$ZipEntryIterator.nextElement(ZipFile.java:495)
> at java.util.jar.JarFile$JarEntryIterator.next(JarFile.java:257)
> at java.util.jar.JarFile$JarEntryIterator.nextElement(JarFile.java:266)
> at java.util.jar.JarFile$JarEntryIterator.nextElement(JarFile.java:247)
> at sun.misc.URLClassPath$JarLoader.validIndex(URLClassPath.java:1017)
> at sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:1150)
> at sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:1062)
> at sun.misc.URLClassPath.getResource(URLClassPath.java:249)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.drools.core.common.CompositeDefaultAgenda.halt(CompositeDefaultAgenda.java:232)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.halt(StatefulKnowledgeSessionImpl.java:1301)
> at org.drools.compiler.integrationtests.CompositeAgendaTest.testCreateHaltDisposeAgenda(CompositeAgendaTest.java:115)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.lang.Thread.run(Thread.java:748)
> Standard Output
> 14:02:49.576 [Time-limited test] INFO o.d.c.k.b.impl.KieRepositoryImpl.addKieModule:111 - KieModule was added: MemoryKieModule[releaseId=org.default:artifact:1.0.0]
> 14:02:49.636 [Time-limited test] DEBUG o.d.c.m.DroolsManagementAgent.registerMBean:210 - Registered org.kie:kcontainerId="f6789948-81a7-428a-8941-6af6283f6219",kbaseId="defaultKieBase" into the platform MBean Server
> {{noformat}}
> detaiils at
> https://rhba-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/KIE/job/7.26.x/j...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (DROOLS-4764) Enhance test org.kie.hacep.PodAsLeaderTest.processOneSentMessageAsLeaderTest to not randomly fail
by Marek Novotny (Jira)
[ https://issues.redhat.com/browse/DROOLS-4764?page=com.atlassian.jira.plug... ]
Marek Novotny updated DROOLS-4764:
----------------------------------
Labels: tests-failures (was: )
> Enhance test org.kie.hacep.PodAsLeaderTest.processOneSentMessageAsLeaderTest to not randomly fail
> -------------------------------------------------------------------------------------------------
>
> Key: DROOLS-4764
> URL: https://issues.redhat.com/browse/DROOLS-4764
> Project: Drools
> Issue Type: Bug
> Reporter: Marek Novotny
> Assignee: Massimiliano Dessi
> Priority: Major
> Labels: tests-failures
>
> There is randomly failing the test {{org.kie.hacep.PodAsLeaderTest.processOneSentMessageAsLeaderTest}} with exception like:
> {{noformat}}
> java.lang.RuntimeException
> at org.kie.hacep.PodAsLeaderTest.processOneSentMessageAsLeaderTest(PodAsLeaderTest.java:99)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.util.NoSuchElementException
> at org.apache.kafka.common.utils.AbstractIterator.next(AbstractIterator.java:52)
> at org.kie.hacep.PodAsLeaderTest.processOneSentMessageAsLeaderTest(PodAsLeaderTest.java:82)
> ... 12 more
> {{noformat}}
> one of the reference https://rhba-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/KIE/job/7.26.x/j...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months