[jira] [Created] (IGNITE-14440) Run external tests in ducktape
Maksim Timonin created IGNITE-14440: --- Summary: Run external tests in ducktape Key: IGNITE-14440 URL: https://issues.apache.org/jira/browse/IGNITE-14440 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin Docker with ducktape should have following volumes: # ignite-dev -> Ignite current branch # ignite-lib -> python lib + java deps in modules/ducktests/tests/ignitetest # ignite-tests -> python tests, default - modules/ducktests/ignitetest/tests # ignite-specs -> specs for tests, structure of directories contain specs (incl. jinja2 templates) should be redefined. Set default value for new directory within ignitetest. # /opt/ignite-* - all distributives. Mount with python libs (lib, tests, specs) must be installed in docker as develop lib (see, python setup.py develop). Notes: # Ordering of installing matters - lib, specs, tests # ignitetest - Manifest.in should skip directories: ./tests, with specs. There should be an util that responsible for uploading ignite dists. Note: # Provide a migration mode for the util. Try copy distributives from existing docker image to local fs to skip downloading them from Internet. # Download new versions by running .sh command. *Nice to have:* replace runtests.sh and ducker-ignite with: # docker-compose.yml describes num of containers, mounts, ports, etc. # entrypoint for docker is a ducktape command. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14303) H2Cursor doesn't match to contract of the GridCursor.
Maksim Timonin created IGNITE-14303: --- Summary: H2Cursor doesn't match to contract of the GridCursor. Key: IGNITE-14303 URL: https://issues.apache.org/jira/browse/IGNITE-14303 Project: Ignite Issue Type: Bug Reporter: Maksim Timonin Assignee: Maksim Timonin Queries like "select max(col) from table" relies on behavior of H2Cursor that differs to GridCursor: # It is not "first before". So H2 invoke cursor.get() first, without cursor.next(). # Then for empty cursor it doesn't expect exception for get. It checks the return value for NULL. Currently we can't do smth with that as this logic is implemented within H2. But Calcite should handle that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14283) Create the Sanity Checks job on TC
Maksim Timonin created IGNITE-14283: --- Summary: Create the Sanity Checks job on TC Key: IGNITE-14283 URL: https://issues.apache.org/jira/browse/IGNITE-14283 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin Assignee: Peter Ivanov 1. The [Build] job runs without any checks. 2. There will be a new job [Sanity Checks], that runs all checks - checkstyle, licenses, javadoc, check-suites. 3. [Sanity Checks] runs in parallel with [Build]. 4. All TC jobs with tests depend on a result of the [Sanity Checks] job. If the check job fails then a test job won't be started. 5. Users can disable the [Sanity Checks] job with a selector on the Parameters tab of custom TC build. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14278) Design public Index API
Maksim Timonin created IGNITE-14278: --- Summary: Design public Index API Key: IGNITE-14278 URL: https://issues.apache.org/jira/browse/IGNITE-14278 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin Assignee: Maksim Timonin There is a feature request - provide opportunity to index non-key fields for non-SQL caches. Need to check opportunity to implement it and design API. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14270) Remove "project" param from Ducktape Specs.
Maksim Timonin created IGNITE-14270: --- Summary: Remove "project" param from Ducktape Specs. Key: IGNITE-14270 URL: https://issues.apache.org/jira/browse/IGNITE-14270 Project: Ignite Issue Type: Task Reporter: Maksim Timonin Currently IgniteSpec supports param "project" that actually is useless. Should be removed to avoid misunderstandings of how to use custom build of Ignite with ducktape tests. Also it's required to review other places that this param is used and verify it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14219) stopAllGrids does not wait for IgniteProcessProxy stop.
Maksim Timonin created IGNITE-14219: --- Summary: stopAllGrids does not wait for IgniteProcessProxy stop. Key: IGNITE-14219 URL: https://issues.apache.org/jira/browse/IGNITE-14219 Project: Ignite Issue Type: Bug Reporter: Maksim Timonin Assignee: Maksim Timonin stopAllGrids does not wait for subprocess stops. In case of running grids in subprocess (IgniteProcessProxy). It just wait for "kill -9" command, but it's performed async. So subprocess with grid may be running for more time and interfere with other tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14206) 2.8.1 inlines POJO but ignores it since 2.9.0
Maksim Timonin created IGNITE-14206: --- Summary: 2.8.1 inlines POJO but ignores it since 2.9.0 Key: IGNITE-14206 URL: https://issues.apache.org/jira/browse/IGNITE-14206 Project: Ignite Issue Type: Bug Reporter: Maksim Timonin Assignee: Maksim Timonin Reproducer https://github.com/apache/ignite/pull/8811/files -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14152) JCache TCK suite runs some Ignite tests.
Maksim Timonin created IGNITE-14152: --- Summary: JCache TCK suite runs some Ignite tests. Key: IGNITE-14152 URL: https://issues.apache.org/jira/browse/IGNITE-14152 Project: Ignite Issue Type: Bug Reporter: Maksim Timonin Assignee: Maksim Timonin There is a wrong configuration of the "jcache-tck" profile. It excludes only "*Test.java" classes, but by default maven runs also "*Tests.java" classes. [1] So, collection IgniteDataIntegrity*Tests* [2] runs for every start of this TC suite. Also after IGNITE-130512 the default collection of test expanded, then there are more tests started to run within the suite and it started to fail by timeout. [1] https://maven.apache.org/surefire/maven-surefire-plugin/examples/inclusion-exclusion.html [2] https://ci.ignite.apache.org/viewLog.html?buildId=5857723=IgniteTests24Java8_JCacheTck11=testsInfo -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14117) Travis ignores JVM_EXTRA_ARGS
Maksim Timonin created IGNITE-14117: --- Summary: Travis ignores JVM_EXTRA_ARGS Key: IGNITE-14117 URL: https://issues.apache.org/jira/browse/IGNITE-14117 Project: Ignite Issue Type: Bug Reporter: Maksim Timonin Assignee: Maksim Timonin Travis failed to resolve some dependencies on jdk.11.0.2. Reason is JDK bug [1]. Workaround is setup -Djdk.tls.client.protocols=TLSv1.2. But it's incorrect to setup it within JVM_EXTRA_ARGS. Maven use MAVEN_OPTS for that [1] [https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8220723] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13796) Update docs for the kubernetes module)
Maksim Timonin created IGNITE-13796: --- Summary: Update docs for the kubernetes module) Key: IGNITE-13796 URL: https://issues.apache.org/jira/browse/IGNITE-13796 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13789) Add 2.9.0 version to ducktape tests
Maksim Timonin created IGNITE-13789: --- Summary: Add 2.9.0 version to ducktape tests Key: IGNITE-13789 URL: https://issues.apache.org/jira/browse/IGNITE-13789 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin Assignee: Mikhail Filatov Changes should be in: # docker # version.py # some existed tests? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13762) MTCGA/Muted tests web page should display multiple Jira tickets in Ticket column
Maksim Timonin created IGNITE-13762:
---
Summary: MTCGA/Muted tests web page should display multiple Jira
tickets in Ticket column
Key: IGNITE-13762
URL: https://issues.apache.org/jira/browse/IGNITE-13762
Project: Ignite
Issue Type: New Feature
Reporter: Maksim Timonin
Some test ignored with multiple jira tickets, they marked as:
@Ignore("https://../IGNITE-12345;, "https://.../IGNITE-54321;)
For example:
PageEvictionTouchOrderTest.testTouchOrderWithFairFifoEvictionMvccTxReplicated
But web of MTCGA displays only first ticket in column "Ticket":
https://mtcga.gridgain.com/mutes.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13728) Ignored load / benchmark tests
Maksim Timonin created IGNITE-13728: --- Summary: Ignored load / benchmark tests Key: IGNITE-13728 URL: https://issues.apache.org/jira/browse/IGNITE-13728 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin Currently load and benchmark tests are marked with the Ignore annotation. So, there should be a registry that contains all such tests to track them. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13723) Lost & Failed Tests
Maksim Timonin created IGNITE-13723: --- Summary: Lost & Failed Tests Key: IGNITE-13723 URL: https://issues.apache.org/jira/browse/IGNITE-13723 Project: Ignite Issue Type: Bug Reporter: Maksim Timonin This is an umbrella ticket for tests that are lost (weren't take a place in any suite) and failed& Now they are marked as Ignored with link to this ticket. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13605) Ducktests test: PDS compatibility for ignite versions
Maksim Timonin created IGNITE-13605: --- Summary: Ducktests test: PDS compatibility for ignite versions Key: IGNITE-13605 URL: https://issues.apache.org/jira/browse/IGNITE-13605 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13604) Ducktests: make a flag to ignore @cluster decorator
Maksim Timonin created IGNITE-13604: --- Summary: Ducktests: make a flag to ignore @cluster decorator Key: IGNITE-13604 URL: https://issues.apache.org/jira/browse/IGNITE-13604 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13561) Fix non-stable test for dynamic indexing
Maksim Timonin created IGNITE-13561: --- Summary: Fix non-stable test for dynamic indexing Key: IGNITE-13561 URL: https://issues.apache.org/jira/browse/IGNITE-13561 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin Assignee: Ivan Daschinskiy Test is not stable: DynamicEnableIndexingConcurrentSelfTest.testConcurrentRebalance Sometimes evict after indexing isn't finished yet while assertions starts. Then "select * from poi" returns invalid number of rows. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13560) Add cluster node attribute colocated BackupFilter
Maksim Timonin created IGNITE-13560: --- Summary: Add cluster node attribute colocated BackupFilter Key: IGNITE-13560 URL: https://issues.apache.org/jira/browse/IGNITE-13560 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin Assignee: Sergei Ryzhov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13512) Provide a check that all test are part of any TestSuite. Alert otherwise
Maksim Timonin created IGNITE-13512: --- Summary: Provide a check that all test are part of any TestSuite. Alert otherwise Key: IGNITE-13512 URL: https://issues.apache.org/jira/browse/IGNITE-13512 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin Assignee: Maksim Timonin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13449) Ducktape selftest checks use java from JAVA_HOME
Maksim Timonin created IGNITE-13449: --- Summary: Ducktape selftest checks use java from JAVA_HOME Key: IGNITE-13449 URL: https://issues.apache.org/jira/browse/IGNITE-13449 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin Selftests are tests that check ducktests environment is correct and test are reliable, and we can rely on their timings and results. Check that ignite.sh uses java set with JAVA_HOME -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13448) Ducktests selftest: time is synchronized on nodes
Maksim Timonin created IGNITE-13448: --- Summary: Ducktests selftest: time is synchronized on nodes Key: IGNITE-13448 URL: https://issues.apache.org/jira/browse/IGNITE-13448 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin Selftests are tests that check ducktests environment is correct and test are reliable, and we can rely on their timings and results. It's required to add test that check that time on all nodes is synchronized (the same). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13447) Python starter of ducktests
Maksim Timonin created IGNITE-13447: --- Summary: Python starter of ducktests Key: IGNITE-13447 URL: https://issues.apache.org/jira/browse/IGNITE-13447 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin run_test.sh is bash script that start docker env locally, configure tests and run ducktape util. But as it written on bash there are some limitations. It's required to replace the script with python starter. Requirements are: # Orchestrate (start/stop/restart) of local environment - should be pluggable (vagrant, docker, minikube); # Configure local cluster with yaml - dynamically configuration num of nodes (depend on running test suites) # Configure tests with yaml: suites, globals, parameters, etc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13434) Add self test checks that java assert leads to python exception
Maksim Timonin created IGNITE-13434: --- Summary: Add self test checks that java assert leads to python exception Key: IGNITE-13434 URL: https://issues.apache.org/jira/browse/IGNITE-13434 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin Add suite with self tests, that checks that ignitetest works correct. First such test must checks that java asserts are converted to python exceptions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13428) Ignite integration tests framework
Maksim Timonin created IGNITE-13428: --- Summary: Ignite integration tests framework Key: IGNITE-13428 URL: https://issues.apache.org/jira/browse/IGNITE-13428 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin Currently Ignite doesn’t have a solution for automated integration testing in real-world distributed environment. This ticket aims to provide such solution. The proposed test framework is based on ducktape [1]. Requirements to integration tests includes: easy start of fair distributed environment locally, run compatibility tests, provide comparison benchmarks between different Ignite versions, integration tests with 3rd party services, parametrize tests and provide clear reports. [1]https://github.com/confluentinc/ducktape [Dev List discussion|http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Ignite-integration-testing-framework-td47579.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13257) Kubernetes example is not working
Maksim Timonin created IGNITE-13257: --- Summary: Kubernetes example is not working Key: IGNITE-13257 URL: https://issues.apache.org/jira/browse/IGNITE-13257 Project: Ignite Issue Type: Bug Reporter: Maksim Timonin Assignee: Maksim Timonin kubernetes module contains config directory that: # contains misleading DEVNOTES.txt that contains non-actual description how to assemble Apache Ignite; # default example isn't worked out-of-the box: ## latest kubernetes complains about deployment API version; ## leads to 403 error while nodes try find each other. -- This message was sent by Atlassian Jira (v8.3.4#803005)
