[jira] [Created] (IGNITE-12757) ignitevisorcmd does not connect to the cluster
Nikolai Kulagin created IGNITE-12757: Summary: ignitevisorcmd does not connect to the cluster Key: IGNITE-12757 URL: https://issues.apache.org/jira/browse/IGNITE-12757 Project: Ignite Issue Type: Bug Affects Versions: 2.8 Reporter: Nikolai Kulagin ignitevisorcmd does not connect to the cluster. The log does not contain any errors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12737) Incorrect annotation on TxDeadlockCauseTest
Nikolai Kulagin created IGNITE-12737:
Summary: Incorrect annotation on TxDeadlockCauseTest
Key: IGNITE-12737
URL: https://issues.apache.org/jira/browse/IGNITE-12737
Project: Ignite
Issue Type: Bug
Reporter: Nikolai Kulagin
Method TxDeadlockCauseTest#testCauseObject() have annotation
{color:#ffab00}@Test{color}, but it is not a test case. As a result, JUnit can
run no one test in this class and printed error.
{code:java}
java.lang.Exception: Method testCauseObject should have no parameters.{code}
Most likely TxDeadlockCauseTest.class was commented on in the suite
TxDeadlockDetectionTestSuite because of this.
I suggest:
1. Delete the annotation {color:#ffab00}@Test{color};
2. Fix the tests in TxDeadlockCauseTest (3 tests look good, 1 test fails);
3. Uncomment the TxDeadlockCauseTest in the suite.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12693) Incorrect operation of the eviction policy internal counter
Nikolai Kulagin created IGNITE-12693:
Summary: Incorrect operation of the eviction policy internal
counter
Key: IGNITE-12693
URL: https://issues.apache.org/jira/browse/IGNITE-12693
Project: Ignite
Issue Type: Bug
Components: cache
Reporter: Nikolai Kulagin
Attachments: EvictionPoliciesReproducer.java
When an entry is added to the cache, its size is added to the internal policy
counter. When the size of the internal counter exceeds the max, entries begin
to evict until the internal size is less than the maximum.
When deleting, the size of the entry is subtracted from the internal counter,
but since when deleting an element, only its key is most often indicated, only
the key size is subtracted. This way you can get the moment when the cache is
empty, but the size of the internal counter is not.
{code:java}
@Override public void onEntryAccessed(boolean rmv, EvictableEntry
entry) {
if (!rmv) {
...
else {
Object node = entry.removeMeta();
if (node != null) {
removeMeta(node);
memSize.add(-entry.size());
}
}
}
{code}
In the worst case, a situation is possible when an object added to an empty
cache is evicted, although it is much smaller than the maximum size.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12317) Add EvictionFilter factory support in IgniteConfiguration.
Nikolai Kulagin created IGNITE-12317: Summary: Add EvictionFilter factory support in IgniteConfiguration. Key: IGNITE-12317 URL: https://issues.apache.org/jira/browse/IGNITE-12317 Project: Ignite Issue Type: Sub-task Components: cache Reporter: Nikolai Kulagin Assignee: Nikolai Kulagin Fix For: 2.9 Some entities on cache configuration are configured via factories, while others are set directly, for example, eviction policy and eviction filter. Need to add new configuration properties for eviction filter factory and deprecate old ones (do not remove for compatibility). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-11087) GridJobCheckpointCleanupSelfTest.testCheckpointCleanup is flaky
Nikolai Kulagin created IGNITE-11087:
Summary: GridJobCheckpointCleanupSelfTest.testCheckpointCleanup is
flaky
Key: IGNITE-11087
URL: https://issues.apache.org/jira/browse/IGNITE-11087
Project: Ignite
Issue Type: Bug
Reporter: Nikolai Kulagin
Assignee: Nikolai Kulagin
Fix For: 2.8
Attachments: #removeCheckpoint isn't called.txt, #removeCheckpointis
called once more.txt
The method of remove a checkpoint is sometimes not called or is called once
more. Test has a very low fail rate, 0 per 360 runs on TC and 1 per 412 on TC
Bot. On local machine approximately 1 failure per 100 runs. Logs in the
attachment.
Test is flaky for a long time. Before replacing IP Finder in IGNITE-10555, test
was slower, which made fail rate even less.
{code:java}
[2019-01-25 14:49:03,050][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError: expected:<1> but was:<0>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:241)
at
org.apache.ignite.internal.GridJobCheckpointCleanupSelfTest.testCheckpointCleanup(GridJobCheckpointCleanupSelfTest.java:88)
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
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:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
at java.lang.Thread.run(Thread.java:748){code}
[^#removeCheckpoint isn't called.txt]
^_^
{code:java}
[2019-01-25 14:50:03,282][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError: expected:<-1> but was:<0>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:241)
at
org.apache.ignite.internal.GridJobCheckpointCleanupSelfTest.testCheckpointCleanup(GridJobCheckpointCleanupSelfTest.java:88)
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
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:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
at java.lang.Thread.run(Thread.java:748){code}
[^#removeCheckpointis called once more.txt]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10779) PagesWriteThrottleSmokeTest.testThrottle is flaky
Nikolai Kulagin created IGNITE-10779:
Summary: PagesWriteThrottleSmokeTest.testThrottle is flaky
Key: IGNITE-10779
URL: https://issues.apache.org/jira/browse/IGNITE-10779
Project: Ignite
Issue Type: Task
Reporter: Nikolai Kulagin
Assignee: Nikolai Kulagin
Fix For: 2.8
Sometimes, at poor checkpoint write speed, put rate degrated to zero for at
least 10 seconds with write throttling enabled. Success rate on TC = 87%. [Test
details|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=2808794487465215609=testDetails]
{code:java}
junit.framework.AssertionFailedError: Put rate degraded to zero for at least 10
seconds
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PagesWriteThrottleSmokeTest.testThrottle(PagesWriteThrottleSmokeTest.java:217)
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 junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2209)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:144)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2124)
at java.lang.Thread.run(Thread.java:748)
{code}
Test became flaky after IGNITE-10028.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10628) Add support for nightly RunAll
Nikolai Kulagin created IGNITE-10628: Summary: Add support for nightly RunAll Key: IGNITE-10628 URL: https://issues.apache.org/jira/browse/IGNITE-10628 Project: Ignite Issue Type: Sub-task Reporter: Nikolai Kulagin Assignee: Nikolai Kulagin Add support for nightly RunAll, fix divisions on the y-axis of duration chart -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10540) [TC Bot] "Compare builds" page with Internal Server Error [500]
Nikolai Kulagin created IGNITE-10540:
Summary: [TC Bot] "Compare builds" page with Internal Server Error
[500]
Key: IGNITE-10540
URL: https://issues.apache.org/jira/browse/IGNITE-10540
Project: Ignite
Issue Type: Bug
Reporter: Nikolai Kulagin
Assignee: Nikolai Kulagin
"Compare builds" page with Internal Server Error [500].
{code:java}
com.google.inject.ConfigurationException: Guice configuration errors:
1) No implementation for org.apache.ignite.ci.user.ICredentialsProv was bound.
while locating org.apache.ignite.ci.user.ICredentialsProv
for field at
org.apache.ignite.ci.tcbot.builds.CompareBuildsService.prov(CompareBuildsService.java:38)
while locating org.apache.ignite.ci.tcbot.builds.CompareBuildsService
1 error
at
com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1075)
at
com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1034)
at
com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1086)
at
org.apache.ignite.ci.web.rest.build.CompareBuilds.tests(CompareBuilds.java:120)
at
org.apache.ignite.ci.web.rest.build.CompareBuilds.sortedTests(CompareBuilds.java:79)
at
org.apache.ignite.ci.web.rest.build.CompareBuilds.getTestFailsComparision(CompareBuilds.java:95)
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.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
at
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)
at
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)
at
org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:205)
at
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)
at
org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)
at
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)
at
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)
at
org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
at
org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)
at
org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305)
at
org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)
at
org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473)
at
org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427)
at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388)
at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341)
at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:857)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:535)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595)
at
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1340)
at
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
at
[jira] [Created] (IGNITE-10203) [TC Bot] Support for alternative configurations for PR testing
Nikolai Kulagin created IGNITE-10203: Summary: [TC Bot] Support for alternative configurations for PR testing Key: IGNITE-10203 URL: https://issues.apache.org/jira/browse/IGNITE-10203 Project: Ignite Issue Type: Task Reporter: Nikolai Kulagin Assignee: Nikolai Kulagin Support for alternative configurations for PR testing (for example, IgniteTests24Java8_RunMl) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10169) Show tests and problems values on graphs
Nikolai Kulagin created IGNITE-10169: Summary: Show tests and problems values on graphs Key: IGNITE-10169 URL: https://issues.apache.org/jira/browse/IGNITE-10169 Project: Ignite Issue Type: Sub-task Reporter: Nikolai Kulagin Assignee: Nikolai Kulagin Show tests and problems values on graphs (currently shows build's start time). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10137) [TC Bot] Add button 'Expand all' on 'PR failures' page
Nikolai Kulagin created IGNITE-10137: Summary: [TC Bot] Add button 'Expand all' on 'PR failures' page Key: IGNITE-10137 URL: https://issues.apache.org/jira/browse/IGNITE-10137 Project: Ignite Issue Type: Sub-task Reporter: Nikolai Kulagin Assignee: Nikolai Kulagin Add button 'Expand all' on '[PR failures|http://localhost:8080/prs.html]' page. The button should show additional information for all available lines. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10125) [TC Bot] Uniform style for buttons
Nikolai Kulagin created IGNITE-10125: Summary: [TC Bot] Uniform style for buttons Key: IGNITE-10125 URL: https://issues.apache.org/jira/browse/IGNITE-10125 Project: Ignite Issue Type: Sub-task Reporter: Nikolai Kulagin Assignee: Nikolai Kulagin Uniform style for buttons: "Inspect" from [PR selection|mtcga.gridgain.com/prs.html], "Show graph" from [Master Trends|https://mtcga.gridgain.com/comparison.html], "More >>" from [PR Failures|https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/5200/head=Latest] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10124) [TC Bot] Redesign and refactor UI
Nikolai Kulagin created IGNITE-10124: Summary: [TC Bot] Redesign and refactor UI Key: IGNITE-10124 URL: https://issues.apache.org/jira/browse/IGNITE-10124 Project: Ignite Issue Type: Task Reporter: Nikolai Kulagin We must make the TC bot more user-friendly, make UI more intuitive and simple -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9849) Remove invalid builds from the selection
Nikolai Kulagin created IGNITE-9849: --- Summary: Remove invalid builds from the selection Key: IGNITE-9849 URL: https://issues.apache.org/jira/browse/IGNITE-9849 Project: Ignite Issue Type: Sub-task Reporter: Nikolai Kulagin Assignee: Nikolai Kulagin In selection sometimes there are builds with abnormal values. For example, the average number of failed tests is 25. But in the build [1953935] there are 2939 failed tests. This is an anomalous value. Need to add the ability to remove it from the selection. Build [1953935] - not valid. In total, 1. While clicking on a point on the chart, show a button that allows marking a build invalid and excludes it from further selections. 2. Reduce the number of erroneous exceptions. Compare the value with the average, if the difference is small - ask for confirmation of the operation. 3. Add the ability to return an excluded build to the selection. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9833) Update Master Trends metrics: add total run time (duration), number of runs
Nikolai Kulagin created IGNITE-9833: --- Summary: Update Master Trends metrics: add total run time (duration), number of runs Key: IGNITE-9833 URL: https://issues.apache.org/jira/browse/IGNITE-9833 Project: Ignite Issue Type: Sub-task Reporter: Nikolai Kulagin Assignee: Nikolai Kulagin Update [Master Treands|https://mtcga.gridgain.com/comparison.html] metrics on TC Bot: add total run time (duration) and number of runs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9805) Make line graphs with animation
Nikolai Kulagin created IGNITE-9805: --- Summary: Make line graphs with animation Key: IGNITE-9805 URL: https://issues.apache.org/jira/browse/IGNITE-9805 Project: Ignite Issue Type: Sub-task Reporter: Nikolai Kulagin Assignee: Nikolai Kulagin Add the ability to view a specific point on the line graph -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9770) Re-run possible blockers from pr.html
Nikolai Kulagin created IGNITE-9770: --- Summary: Re-run possible blockers from pr.html Key: IGNITE-9770 URL: https://issues.apache.org/jira/browse/IGNITE-9770 Project: Ignite Issue Type: Sub-task Reporter: Nikolai Kulagin Assignee: Nikolai Kulagin Show button for re-run possible blockers. Also show merged button with re-run possible blockers JIRA, so the user re-run the possible tests and does not wait for them to complete,but learn about the completed tests from the comment to GitHib. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
Nikolai Kulagin created IGNITE-9541: --- Summary: Add the comparison for two general statistics "RunAll" for master in the date interval Key: IGNITE-9541 URL: https://issues.apache.org/jira/browse/IGNITE-9541 Project: Ignite Issue Type: Sub-task Reporter: Nikolai Kulagin Based on IGNITE-9333 add the comparison for two general statistics "RunAll" for master in the date interval -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module
Nikolai Kulagin created IGNITE-9165:
---
Summary: FindBugs: Methods may fail to close stream in core module
Key: IGNITE-9165
URL: https://issues.apache.org/jira/browse/IGNITE-9165
Project: Ignite
Issue Type: Bug
Components: binary
Affects Versions: 2.6
Reporter: Nikolai Kulagin
Assignee: Nikolai Kulagin
Fix For: 2.7
Attachments:
findbugs-result-apache-ignite[ignite-core]_2018_08_02_12_38_02.html
The method creates an IO stream object, does not assign it to any fields, pass
it to other methods that might close it, or return it, and does not appear to
close the stream on all paths out of the method. This may result in a file
descriptor leak.
Example:
{code:java}
// GridCacheAbstractLoadTest#GridCacheAbstractLoadTest()
try {
props.load(new FileReader(GridTestUtils.resolveIgnitePath(
"modules/tests/config/cache-load.properties")));
}
catch (IOException e) {
throw new RuntimeException(e);
}{code}
One of possible solutions:
{code:java}
try(Reader reader = new FileReader(GridTestUtils.resolveIgnitePath(
"modules/tests/config/cache-load.properties"))) {
props.load(reader);
}
catch (IOException e) {
throw new RuntimeException(e);
}{code}
List of classes in "core" module:
+org.apache.ignite.internal:+ * *BinaryContext*#classesInPackage(String) ,
line 583
* *GridClientJdkMarshalle*r#marshal(Object, int), line 61
*
*IgniteExplicitImplicitDeploymentSelfTest*$GridDeploymentResourceTestJob#execute(),
line 474
* *OptimizedObjectStreamSelfTest*#testReadLine(), line 793
* *PageIdDistributionTest*#_testRealHistory(), line 220
* *HttpIgniteUpdatesChecker*#getUpdates(boolean), line 69
* *IpcSharedMemoryNativeLoaderSelfTest*#readStreams(Process), line 207
+org.apache.ignite:+
*GridCacheAbstractLoadTest*#GridCacheAbstractLoadTest(), line 123
*GridTestUtils*.sslContext(), line 1674
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9160) NPE and CCE on equals() methods
Nikolai Kulagin created IGNITE-9160: --- Summary: NPE and CCE on equals() methods Key: IGNITE-9160 URL: https://issues.apache.org/jira/browse/IGNITE-9160 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.6 Reporter: Nikolai Kulagin Assignee: Nikolai Kulagin Fix For: 2.7 Next classes have exceptions in equals() method: *GridDhtPartitionFullMap -* NPE *GridDhtPartitionMap* - NPE *GridNearOptimisticTxPrepareFuture* - NPE and CCE *GridCacheMvccCandidate* - CCE *GridDhtPartitionExchangeId* - CCE *GridTuple6* - CCE -- This message was sent by Atlassian JIRA (v7.6.3#76005)
